Artifacts

The chat ends. The artifact stays.

Your coding agent writes a short Markdown file. artifacts turns it into one polished HTML page, with diagrams, charts, drill-downs and diffs, that you can read, mark up and share as a link.

Try it

npm i -g @phnx-labs/artifacts-cli        # Node 20 or later

artifacts new report --out report.md     # a starter file
artifacts render report.md --open        # the page, re-rendered on every save

Then give your agents the skill, so they write artifacts for you:

agents skills add gh:phnx-labs/artifacts-cli --names artifacts --agents claude,codex -y

(That uses agents-cli. Run artifacts auth login once to share pages as links with artifacts share report.md.)

Share a video

Signed-in users can publish organization- or owner-only recordings directly:

artifacts share recording.mp4 --visibility org --expire never

For eligible managed accounts, videos over 20 MiB upload in resumable 50 MiB parts. If the command is interrupted, run it again with the same file and options; completed parts are recovered from ~/.artifacts/uploads/. Progress appears only in an interactive terminal. Shared videos support byte-range playback, so viewers can seek without downloading the whole recording first.

On an endpoint with media keys bound, an uploaded recording is transcribed and summarized in the background. Its page then shows captions, chapters, the summary, timestamped action items and a searchable transcript you can click to seek; links like …/standup.mp4?t=90 open at that moment. The transcript, captions and summary are readable by exactly the people who can watch the video. The job's deadline is durable: if background processing or the final listing-metadata rewrite is interrupted, both share media status and share list --meta media=failed report the failure without requiring someone to open the video page.

artifacts share media status https://share.getrush.ai/you/standup.mp4   # pending, ready or failed
artifacts share media retry  https://share.getrush.ai/you/standup.mp4   # rerun a failed job
artifacts share list --meta ticket=PHNX-4287                              # recordings that mention it

Operators turn this on with secrets exec <bundle> -- artifacts share update --media-keys, which binds DEEPGRAM_API_KEY, OPENROUTER_API_KEY and MEDIA_JOB_SECRET from the environment. Summaries go through OpenRouter with zero data retention.

Why

• About 90% fewer tokens. The agent writes content, not HTML and CSS. A plan that takes 25,028 tokens as HTML takes 2,391 as Markdown.
• Real components from plain text. Charts, drill-downs, diffs and forms come from a few lines of JSON or a table.
• The page talks back. Readers highlight, leave notes and answer worksheet questions on the page; your agent reads them with artifacts notes and artifacts answers.
• Every version stays. Each render is saved locally, so earlier versions reopen with artifacts history.
• One file, safe to send. The HTML works offline, in light and dark. Embedded HTML is sanitized, and a page is checked for credentials before it is shared.

Learn more

See the whole loop at artifacts-cli.sh. Every command explains itself with artifacts <command> --help; every command and option is in the command reference (Markdown index).

License

Apache-2.0