How it works
agent-paste is built for work an agent generated and a person needs to inspect. The safety model is straightforward: keep each Workspace separate, isolate generated content by origin, use unguessable URLs, and let handoffs expire.
Artifacts, audit records, and settings belong to a Workspace. A publish from one Workspace is not mixed with another Workspace's data.
Human sign-in, CLI credentials, and MCP OAuth are checked against that boundary. A credential can publish for its Workspace, but it is not a broad pass into the rest of the system.
Artifact files are encrypted and stored privately. Viewers never receive raw storage links. They receive an unguessable capability hostname backed by signed authorization.
That URL is a controlled handoff, not a public bucket address.
Agent output is treated as untrusted. Each Artifact runs top-level on a separate capability origin, away from the dashboard and account session.
That separation matters most for generated HTML. The page you inspect can be useful without being treated as part of the trusted app.
Delete an Artifact when its URL should stop working, or let Workspace Auto Deletion expire it. Platform deny controls can disable abusive content immediately.
Stored credentials are scoped and replaceable. Secrets are shown once when created and stored in non-recoverable verifier form.
An agent should use the CLI when it can run commands. Check whoami --json first. An injected AGENT_PASTE_API_KEY or saved login credential needs no further login. For headless setup, create a key at https://app.agent-paste.sh/keys and inject it through secret configuration. Without a usable credential, use login --device-code in a sandbox and keep it running while the human approves in their own browser. A hosted tool without a shell uses OAuth-only MCP.
Choose --ephemeral when no authenticated path is available and static output meets the task, or accountless publishing is requested. It ignores existing credentials and is not an automatic fallback for authentication failures. Ephemeral Workspaces have short-lived credentials, low write caps, 24-hour cleanup, and noindex.
Ephemeral HTML stays static until claimed: scripts, connections, forms, frames, objects, and workers are blocked.
agent-paste does not inspect or certify uploaded content as safe, and it does not promise malware detection. The enforceable controls are separation, signed access, expiration, rate limits, revocation, and deletion.
It is also not permanent storage and not a deploy platform. Keep your source. Use agent-paste for the handoff.
agent-paste is owned and operated by Zaks.io, LLC. The repo is zaks-io/agent-paste for anyone curious.