agent-paste

Agent Paste turns files your agent creates into websites you can open and send to someone else. Publish a report, a prototype, or a folder of generated HTML and assets. The recipient gets a link they can open without an account.

Why use it?

An agent can build something useful and leave it sitting in a local folder. Agent Paste handles the next step: putting that work on the web so someone can actually look at it. You don't need to set up a hosting project for each result.

• Send a generated report to a teammate who doesn't have your working directory.
• Open an interactive HTML demo in the browser to try what the agent built.
• Ask for changes and publish them to the same link. Recipients see the update when they refresh. Images and other static assets reuse the browser cache for up to one hour; a hard refresh picks up asset changes immediately.

It hosts the files you publish. For an app with a server or database, host those services separately.

Try it without an account

Publish an existing file or folder:

npx @zaks-io/agent-paste publish ./report --ephemeral
# https://01234-56789-abcde-fghjd.agent-paste.link/

Open the returned link to view your work. Accountless publishes expire after 24 hours and render static content. JavaScript, scripted connections, and forms are blocked until you claim the result. The command also returns a claim link if you want to keep it.

For interactive demos, authenticate with a login credential or API key before publishing.

Quick start

npx @zaks-io/agent-paste whoami --json
npx @zaks-io/agent-paste publish ./report

A successful result identifies the Workspace, actor, and scopes. Only authenticated: false means no usable local credential exists. An existing login credential or an injected AGENT_PASTE_API_KEY authenticates automatically; no login is needed. For CI or a headless agent, create a key at API Keys and inject its secret through your sandbox or CI secret configuration. Keep it out of commands and logs.

If authenticated is false, run npx @zaks-io/agent-paste login locally, or npx @zaks-io/agent-paste login --device-code in a sandbox or SSH session. Keep device login running while you approve its displayed URL and code in your own browser, then check whoami again. Device login needs network access to WorkOS and the API, but no browser in the sandbox. Authentication errors require fixing the credential; an invalid environment key overrides a saved login. See the authentication guide.

Expected output:

✓ Published "report"

  View      https://01234-56789-abcde-fghjd.agent-paste.link/
  Expires   <expiration date>
  Upload    3/3 uploaded, 0 reused · 42 KB sent, 0 B cached

  Update    npx @zaks-io/agent-paste publish ./report --artifact-id 01234-56789-abcde-fghjd
            (revises this Artifact; the same link shows the latest revision)

  → open https://01234-56789-abcde-fghjd.agent-paste.link/

Use the artifact ID with --artifact-id to update the same website. Full URLs also work. Updates require Workspace access.

The same ID works with pull to read one stored file, edit to apply literal find-and-replace edits as a new revision, and download to save a revision as a zip. See the command reference.

Use it with your agent

Agents that can run commands should use the CLI. Install the agent-paste skill for Claude Code and Codex to give them the publishing workflow:

npx skills add https://github.com/zaks-io/agent-paste/tree/main/skills/agent-paste \
  --agent claude-code codex

Then ask your agent to publish the files it created with Agent Paste and return the link. The agent skill covers API keys, login, accountless publishing, and updating an existing Artifact.

Agents without a shell can connect to https://mcp.agent-paste.sh and authenticate with OAuth. Its eleven tools publish, revise, edit, list, read, and delete Artifacts and submit feedback, and MCP publishing accepts text only. Use the CLI for folders, binary files, and accountless publishing. See the MCP setup guide.

Send product feedback with agent-paste feedback "Your feedback", or pipe text to agent-paste feedback. Hosted agents can call the MCP feedback tool. Feedback requires authentication and accepts read-only credentials.

What to know before publishing

Anyone with an Artifact's link can view it without signing in. Treat the link as access to its contents.

Authenticated publishes support HTML, CSS, JavaScript, and external HTTPS dependencies. Each Artifact runs on its own origin, separate from the dashboard. Service workers are unsupported.

Each file is served with the content type its extension implies. HTML runs as a website, and images, audio, video, and text open in the browser's built-in viewer. Markdown is served as its raw source, not converted to HTML. PDFs and unrecognized file types download instead of opening.

Each published revision is also packaged as a zip bundle. Save it with agent-paste download <artifact-id>. Hosted agents get its download link from the MCP read_artifact tool.

For the full list of shipped features, see features. For automation details, see the CLI contract. For content policies and storage internals, see content rendering and architecture.

Repository

The hosted service is a set of Cloudflare Workers backed by Postgres and private R2 storage.

Path	Purpose
apps/api	Authenticated control plane, publish coordination, capability manifests.
apps/upload	Upload sessions and byte ingestion into private R2.
apps/content	Serves Artifact bytes on agent-paste.link hosts and legacy signed URLs.
apps/web	Dashboard, authentication, claim, and billing at app.agent-paste.sh.
apps/apex	Marketing site, docs, and agent discovery files at agent-paste.sh.
apps/mcp	OAuth MCP server for hosted agents.
apps/jobs	Cron sweeps and queue consumers for expiry, purge, scans, and bundles.
apps/cli	Published @zaks-io/agent-paste command.
apps/evals	Development-time evals for agent onboarding flows. Not product runtime.
apps/stream	Dormant Live Updates Worker kept for migration history. Not in use.
packages/*	Shared contracts, database, auth, tokens, storage, billing, and UI code.
skills	The agent-paste skill for Claude Code and Codex.
examples	Fixtures for local smoke tests and the CSP proof page.

To develop locally, follow CONTRIBUTING.md and docs/development.md. pnpm verify is the repository gate.

To understand the system, start with docs/ops/project-status.md, then CONTEXT.md, docs/specs/README.md, and docs/adr/README.md.

Licensed under Apache-2.0. The hosted service is operated by Zaks.io, LLC.