Outbox is the private library where your agents' artifacts live: every page, demo or dashboard with its own URL, versioned and ready to share. Yours and presentable, not trapped in a chat.
$ npm install -g @out-box/cli$ outbox loginFree forever with 1 daily document · no card.
# My agent, after its morning routine await outbox.publish({ slug: "briefing-2026-05-19", title: "This morning in Jonathan's head", body: html, visibility: "private", }) ✓ Published → https://out-box.dev/jonathan/briefing-2026-05-19
Works with the agents you already use
My 6am cron drops the briefing at a fixed URL. I stopped opening five apps to start my day.
The weekly per-client status is written by an agent and I just send the link. Private until I decide to share it.
Real versioning for what my agents generate. I can roll back and see what changed, without pasting anything into a doc.
01 · The problem
A page, a dashboard, an interactive demo, a draft. Your agent generates it in seconds and it ends up buried in a conversation you'll close tomorrow and never reopen. No URL, no history, impossible to show a client.
With Claude Artifacts or ChatGPT's canvas, the artifact lives inside the chat: you can't version it, it has no stable link, it isn't yours. Every time you want to present it, you copy and paste it somewhere else.
Outbox is the outbox: the artifacts your agents create land in your library with their own URL, versioned and shareable. Private by default, presentable when you decide.
| When your agent creates an artifact… | Outbox | Claude / Codex | The chat | Notion / wiki | A blog |
|---|---|---|---|---|---|
| Permanent, citable URL | ✓ | ✓ | ✗ | ~ | ✓ |
| Automatic versioning | ✓ | ✓ | ✗ | ~ | ✗ |
| An archive that grows on its own | ✓ | ✓ | ✗ | ~ | ~ |
| Public or private, your call | ✓ | ✗ | ✗ | ~ | ~ |
| Works with any agent, no lock-in | ✓ | ✗ | ✗ | ✗ | ✗ |
| Yours: export it, own the namespace | ✓ | ✗ | ✗ | ~ | ~ |
~ = possible, but by hand or with friction · Claude / Codex = publishing built into a single tool (Artifacts, Sites)
02 · How it works
Outbox doesn't ask you to order folders, tag, organize. Your agent publishes; you search; when needed, you share a link. Subject: the agent. You show up when needed.
publish()
An HTTP call with HTML, slug, visibility. The agent decides. No UI, no forms. It's API-first because its author is code.
POST /publish { "slug": "status-prado-q2", "body": "<article>…</article>", "visibility": "private" }
browse()
Every publication is a real URL, indexed by slug and date. Your private archive (management panel, sees everything) builds itself: by tags, by agent, by visibility. Full-text searchable.
GET /library → your private archive (sees everything) GET /jonathan/status-prado-q2 → a page from your profile GET /library?q=prado → full-text search
share()
Private by default. When you decide, you generate an unlisted link or make it public. Whole folders too. Access is granted, not leaked.
POST /api/share { "slug": "status-prado-q2", "visibility": "unlisted" } # → unguessable link
03 · Anatomy
The core case: an agent reads the HTML that already exists, adds what's new today and re-publishes it. Each re-publish creates a version; the history is navigable and nothing gets overwritten.
A living document: it starts with the agenda at 7am and ends the day with tomorrow's to-dos — without you touching a thing.
04 · What it's for
Not demos: real flows, each ~30 lines on the agent side. Each one with its own URL, its own style, and an archive that grows on its own.
out-box.dev/vos/briefing-hoy
An agent reads yesterday's mail, calendar and Slack and leaves you a private summary. You start without opening 10 windows.
out-box.dev/vos/clientes/solera
Jira + commits + meetings on a per-client page. Private folder; link to the partner when you decide.
out-box.dev/vos/kpis
MRR, active users, NPS: always at the same known URL, ready to show in Monday's meeting.
out-box.dev/vos/repo/semana-20
A per-commit hook builds the monorepo summary and flags regressions. Useful when you come back from vacation.
out-box.dev/vos/research/competidores
An agent compares competitor features, releases and blogs. Archived to cite in your next proposal.
out-box.dev/vos/today
Every task an agent closes gets appended to your page for the day. By the end you have a journal you never wrote.
Not just HTML
Real interactive pages, published like any other Outbox page: public, shareable, yours. They run entirely client-side.
A date range that recalculates KPIs, tabs that swap charts, animated bars, line and cohorts.
Open demo →Live filters by status and area, a count that updates, and items that expand inline.
Open demo →A river that meanders and remakes itself: a flow field with real tidal physics, the moon pulls and the current rotates. Just HTML.
Open demo →05 · Versioning
Every time an agent republishes the same slug, Outbox saves a new version. The full history stays accessible: you can compare, roll back, or see who changed what.
every publish is a version with date and author
go back to any previous version in one command
compare two versions side by side
07 · Artifacts mode
A published page isn't a dead end. The reader selects a fragment, comments on it, and walks away with a feedback packet ready to paste into whichever agent they want. You close the loop, not the tool.
The team starts the quarter with three focuses: retention, onboarding and the library redesign.
Retention hinges on an experiment that isn't validated yet before we commit roadmap.
Onboarding stays on the current flow until the redesign ships.
This clashes with what we closed on Friday: the experiment is already validated, no need to repeat it.
Mark the exact part of the published content you want feedback on.
Leave the note anchored to the fragment, not to the whole page.
Copy the packet (selection + comment + link) and paste it into whichever agent you prefer.
The inspector runs in the reader's browser. Outbox doesn't host the agent or run the model: it just hands you the context so the loop stays yours.
06 · Access control
Every document is born private: only you and your agents see it. Sharing is an explicit, reversible decision — document by document.
Only you and your agents. No one else sees it, not even with the link.
Anyone with the secret link can view it. Great for sharing quickly.
Visible to everyone and listed on your profile. Your work, on display.
When an agent runs in the cloud, you don't hand it the keys to everything. You issue a scoped key: what it can do, in which folder and for how long. If it leaks, the blast radius is one folder, not your whole archive.
clientes/solera/*07 · Integrations
Same agents-first backend, three clients. Pick the one that best fits your workflow; or combine them.
out-box publish
For devs who already live in the CLI. One verb and the URL is in your clipboard. Login via browser handoff, no tokens to paste.
# npm package: @out-box/cli $ npm i -g @out-box/cli $ out-box login $ out-box publish briefing.html → URL copied to clipboard
skills add
Install the skill in Claude Code, Cursor, Codex, or OpenCode. Your agent understands 'publish this to my Outbox' or 'append it to notes/today'.
# install the skill (skills.sh-compliant) $ npx skills add jonathanleiva15/out-box-skills # then, to your agent: > publish this to my Outbox
POST /publish
83 REST endpoints for custom integrations. Zapier, n8n, Make, Custom GPTs, your own scripts: anything that can make HTTP calls.
# publish endpoint $ curl -X POST https://api.out-box.dev/publish \\ -H "Authorization: Bearer outbox_..." \\ -d @briefing.json
08 · Privacy
Outbox is not a social network or a "feed". It's a private archive with the option to share when you decide. The technical decisions reflect that.
Every publication is born private. Only you can read it. Changing it requires an explicit action.
Nothing your agents publish is sent to an external AI provider. Outbox is only storage + delivery.
No Google Analytics, no Facebook pixel, no HotJar. Just Cloudflare Web Analytics server-side, no cookies.
API keys are stored hashed (SHA-256). If you revoke them, they die instantly. Plaintext is shown only once.
09 · Pricing
Free is real and forever. Unlimited versions, full API and CLI on every plan; you only pay for more daily documents.
Launch pricing. Subscribe now and keep this price: it normalizes in September 2026.
To try the flow with one agent and let it run without thinking.
For a person with several agents running for real.
monthly billing
Solopreneur with many agents or creator with several dailies in parallel.
monthly billing
No product caps. For whoever runs many agents at full tilt and doesn't want to think about limits.
monthly billing
Shared workspace, roles, joint audit log and SSO. We're building it with a small group before opening to everyone.
per-seat billing · indicative early-access price
10 · Questions
Have one that isn't here? Write us at hola@out-box.dev.
Your first URL in under two minutes.
$ npm install -g @out-box/cliFree forever with 1 daily document · no card