The chat ends.
The artifact stays.
A plan you approve, a report you forward, a page your team comments on. Your agent writes a short Markdown file; artifacts-cli renders it as one polished HTML page that you read, share and discuss.
$npm i -g @phnx-labs/artifacts-cli
See how it works
artifacts render plan.mdShip the Markdown rendererDRAFT
Why
Agents spend most of their output rebuilding page chrome for every plan.
Scaffold. Preview. Share.
$ artifacts new plan --out plan.md wrote plan.md $ artifacts check plan.md error:2 Frontmatter field "surface" is required for plans. agent adds surface: cli and checks again $ artifacts check plan.md ok
$ artifacts render plan.md --open wrote plan.html served locally the agent saves plan.md, the open page re-renders
Real renders, not mockups.
Every tile is a render of a file in the repository's examples/ folder. Each page is a single HTML file that works offline, in light and dark. Point at a tile to see the fence that made it.
```explorer
{ "title": "Where the cleanup is",
"metric": { "unit": "%", "max": 100 },
"items": [ { "label": "Web", "value": 25 }, … ] }
```The agent writes the content. The renderer writes the page.
The agent never writes component HTML, CSS or JavaScript. It writes a few lines of data, and the renderer builds the finished, interactive component.
--- kind: visual title: Where the dead code is --- ## Story Most removable code sits in two services. ## Figure ```explorer { "title": "Removable code", "metric": { "label": "Removable", "unit": "%", "max": 100 }, "items": [ { "label": "Web", "value": 25 }, { "label": "API", "value": 10 } ] } ```
It learns the format from the CLI
The artifacts skill teaches the workflow, and artifacts components --json prints each component's input with an example to copy.
Mistakes come back with line numbers
artifacts check rejects unknown fields, missing sections, out-of-range values and unsafe HTML before anyone reads the page.
The renderer adds everything else
Layout, light and dark themes, the cover, contents, collapsible sections, code highlighting, math and provenance from git.
Your brand, set once
Put your colors and fonts in DESIGN.md. Every artifact from every agent uses them.
A tenth of the tokens. One look. Checked first.
Any agent
Claude, Codex, Gemini and others render through the same design, so a page looks the same whichever agent wrote it.
Components from fences
explorer, bar-chart, diff, excerpt and field take JSON, a table or a single line.
Cites real code
An excerpt reads the lines from your git checkout and links them to the exact commit, so they can't be misquoted.
Built for reading
A contents rail, collapsible sections, a references list and review threads on shared pages.
One file, anywhere
The HTML works offline. Keep it in your repository or share a link.
Safe by default
Embedded HTML and SVG are sanitized, and a page is scanned for emails and credentials before it is published.
Two commands.
Needs Node 20 or later.
npm i -g @phnx-labs/artifacts-cli
agents skills add gh:phnx-labs/artifacts-cli \ --names artifacts --agents claude,codex -y