Skip to main content

Commands

Discoverable help: artifacta <command> --help shows flags, exit codes, and a worked Examples block on every command. The root artifacta --help also lists every ARTIFACTA_* environment variable, the four exit codes, and a Common workflow guide.
Use push --transcript and ls --transcript to store and filter a session’s conversation; see the session transcript guide for precedence and automation.

Artifact Pages commands

publish

Uploads a local file as an artifact and immediately publishes it as a shareable page. Visibility defaults to unlisted (accessible via URL, not indexed). The page URL is printed to stdout.

unpublish

Takes down an artifact’s public page. The underlying artifact is not deleted. Accepts an artifact ID (art_...) or a page slug (pg_...). The page_id is printed to stdout on success.

Global behavior

Auto-JSON for agents: When stdout is not a TTY (piped or redirected), the CLI automatically outputs JSON. Human-readable output goes to stderr, data to stdout. This means artifacta ls | jq just works.

Destructive actions

The CLI carries verbatim warnings on every destructive command. Read them via --help once before a script run — the wording below is the exact text the CLI prints, and is part of the user-facing contract.
artifacta rm --help — Warning: --session deletes every artifact in that session. Use --dry-run to preview.
artifacta session seal --help — Warning: Sealing is irreversible. Sealed sessions cannot accept new artifacts.

Environment variables

Agent integration pattern: An orchestrator sets ARTIFACTA_SESSION_ID (and optionally ARTIFACTA_MODEL) once in the environment. Every sub-agent inherits them automatically — zero flag passing required. Explicit --model or --meta model= always beats the environment value.

Shell scripting patterns