Client deliverables
Publish a prototype behind an allowlist, let the client comment on specific elements, and republish to the same link. One of our client consoles went through 14 versions in a day.
Artifact Use
Agents finish work as artifacts. Artifact Use gives each one a link, a gate and a review thread the agent can act on.
Any agent publishes HTML tools, dashboards, briefs, prototypes and whole static sites through MCP, a CLI or an API. Reviewers open one stable link without creating an account, comment on the exact element they mean, and the agent reads those comments and ships the next version to the same URL. It all runs on your own Cloudflare account.
- Language
- TypeScript
- Runs on
- Cloudflare Workers, R2, D1
- Licence
- MIT
223artifacts published on our own instance
816versions shipped to stable links
546review comments
19 minmedian from a reviewer’s comment to the agent’s reply
Why we built it
Agent output kept getting lost. Chat artifacts were buried in sessions and locked to one vendor’s accounts, emailing a client an HTML file felt like 1995, and the client’s feedback never made it back to the agent.
We built Artifact Use so that the unit of agent work is a URL. Ship v1, reviewers comment on the page, and the agent ships v2 at the same link. It went from first commit to production in a day, and every demo, brief, spec and brand kit we make now ships through it.
What it does
- Publish from any agent: a hosted MCP endpoint with OAuth, a local MCP server, a JSON CLI, and plugins for Claude Code and Codex
- Viewers need no account: public, email, verified-email and allowlist gates, plus passcode, expiring and per-recipient links
- Comments that reach the agent: pinned to a page element, threaded and resolvable, delivered by long-poll or signed webhook
- Immutable versions at a stable URL, with change notes, rollback, per-file diffs and protection against overwriting a teammate
- Real backends without leaked secrets: the _api/ proxy adds the stored secret and the viewer’s identity on the server
- Safe by default: agents never hold cloud credentials, publishes containing credentials are refused, and links stay unlisted
- Self-hosted on Cloudflare Workers, R2 and D1 under the MIT licence
Where it’s going
- Self-hosting in fifteen minutes with one-command setup
- Artifacts that keep themselves current: a scheduled agent sweeps new comments and stages fixes for the publisher to approve
- Review wherever you work, with the comment inbox inside Claude, ChatGPT, Cursor and VS Code
- Custom domains, collections, and pick-and-vote visual reviews
Who it’s for
Live demos with private backends
The gated page calls your backend through the proxy, so secrets stay on the server and every request carries the viewer’s identity.
Design reviews
Logo rounds and brand kits shared as one link. Reviewers mark their picks and the agent narrows the next round.
Get started
# Claude Code
claude plugin marketplace add iofold/artifact-use
claude plugin install artifact-use@artifact-use
# Codex
codex plugin marketplace add iofold/artifact-use
codex plugin add artifact-use@artifact-use
# Any agent that reads SKILL.md
npx skills add iofold/artifact-usecd apps/worker
npx wrangler d1 create artifact-use
npx wrangler r2 bucket create artifact-use
npx wrangler d1 migrations apply artifact-use --remote
npx wrangler email sending enable updates.example.com
npx wrangler secret put SESSION_SECRET
npx wrangler secret put WORKOS_CLIENT_ID
npx wrangler secret put WORKOS_API_KEY
npx wrangler deployFull documentation is in the repository README.
Work with us
Tell us what the work is, what data it touches and what constraints apply. We’ll work out what to build and how to measure it.