Quickstart

Artifact Publisher, by Currico, turns the HTML your agent finished — a report, proposal, dashboard, microsite, or lightweight app — into a stable unlisted link anyone can open in a browser. Recipients need no account, no repo, and no explanation.

Start by sharing

Feedback is available when a deliverable needs review, but it is not required to publish. Create a workspace, connect your agent, publish HTML, and send the link. Add page-level feedback, versioned updates, and revocation when the workflow calls for them.

What you need

• A Currico account on a deployment where self-serve onboarding is active. v1 provisions one personal workspace.
• An agent or client that supports MCP.
• A finished, self-contained HTML document no larger than 10 MiB of UTF-8.
• A recipient for the unlisted link, when you are ready to share.

1. Create your account and workspace

Go to Your workspace, sign in, and create your personal workspace. The first setup mints a scoped publisher key and shows it exactly once inside a ready-to-run Claude Code command.

Save the setup command while it is visible

The command contains the new publisher key. Copies may remain in your clipboard, Claude Code stores it in local configuration, and your shell may retain it in terminal history after you paste it. Use it only on a trusted machine, clear the clipboard after setup, and remove the history entry if your shell records it. The key and command disappear from the workspace page after refresh or dismissal; Artifact Publisher stores only a hash, so a lost key must be replaced rather than recovered.

Self-serve onboarding is available only on deployments where accounts have been activated. An inactive deployment states that directly on the workspace page.

2. Add Artifact Publisher to Claude Code

On the one-time setup panel, select Copy setup command and paste it into a trusted terminal where Claude Code runs. The command already includes the newly minted key in its Authorization: Bearer header, so there is no separate token lookup for standard setup.

Do not paste the command into a prompt, source file, repository, or artifact. The workspace page also offers a variable-reference example as an advanced alternative for other MCP clients or secret managers.

Read the MCP integration guide for other clients and the full tool lifecycle.

Optional: Configure workspace defaults

A workspace holds your artifacts and the defaults new links inherit. Use configure_workspace to read or change comments_enabled, default_expiry_seconds, and default_artifact_title. The 10 MiB ceiling, rate limits, two-origin isolation model, object storage layout, and security headers are platform guardrails, not client configuration.

3. Publish and share

1. Publish. Call publish_artifact with a title and a self-contained HTML document. The result includes an artifact identifier and a stable unlisted link.

2. Share. Send that link through the channel you already use. Recipients need a browser and the link — not an account, repository, or client install.

3. Update. Call update_artifact when the work changes. It appends a new immutable version while the stable link resolves to the current one.

4. Revoke. Call revoke_artifact when the page should no longer be served. The link stops resolving to content going forward.

Self-contained matters: include the markup, styling, and other resources the document needs inside the HTML. Artifact Publisher is not a general web host or an asset pipeline, and the artifact sandbox blocks all network access, so a document that depends on external fonts, images, or APIs will not render as intended.

Optional feedback

When a recipient needs to react, they can leave a page-level comment. No account is required — the link is the access grant. Your agent calls get_feedback to retrieve structured comments with the version each was left on, and reply_to_feedback to respond in the thread. Feedback is page-level, not DOM- or line-anchored.

Unlisted is not authenticated

Anyone holding a live link can open it, including someone it was forwarded to. Unlisted links are not indexed or listed publicly, but they are possession links. Use revocation if a link should no longer work; it cannot recall material someone already viewed, downloaded, or captured.

Current limits

• One self-contained HTML document per artifact, up to 10 MiB of UTF-8
• Page-level comments only; no DOM- or line-anchored feedback
• Unlisted possession links by default — not per-recipient identity or access auditing