A live, shareable view of everything your coding agent makes — one link per artifact, one live page per session, across any agent.
The shift
Stuck on one machine. Invisible from a cloud agent. Won't open on your phone. Awkward in git — you don't want to commit a throwaway.
A real link, hidden behind a readable title. Opens anywhere, sandboxed, expires on its own, and rolls into one live session page.
User stories
As someone working with a coding agent, when it generates an HTML artifact and its related files, I want them published to a link automatically instead of a local file path — so I can open them from my phone or send them to a teammate without hosting anything myself.
As a user, when the agent hands me the link,
I want it to show up as a clickable link in whatever I'm using — a readable
title (“plan”, “prototype”) in a chat UI, or a clean tappable URL ending in …/plan in a
terminal — so I just click it, and never copy a file path.
As a user, when the agent finishes and gives me its summary, I want it to include a link to my protocontent session page — the one page that lists everything it made — so I land in a single place to review the whole run.
As a user watching my agent work, when it creates or updates a file, I want the session page to update on its own — a new version, a new file appearing — so I get a live view of what my agent is producing, even from another screen.
As a user, because these are prototypes and plans, I want them to live entirely outside my repo — never staged, never committed — and expire on their own — so my git history stays clean and nothing ephemeral ever leaks into source control.
As a user, I want published artifacts isolated on a separate origin — so a generated page can never reach my session, cookies, or files.
As someone who uses more than one coding agent, I want this to work the same from all of them — so I'm not locked into one vendor's artifact panel.
As a user, I want to turn protocontent on in any coding agent I use — as easily as copying one command, or just telling the agent to set it up — so it takes seconds, works wherever I work, and there's nothing to configure.
The product, in two surfaces
Each file the agent makes gets its own sandboxed URL on a random subdomain, surfaced as a clickable
link — a title where the surface renders it, a clean …/name URL where it doesn't.
Re-publishing the same name updates it in place.
Every session gets one subdomain that lists everything the agent produces, and updates the moment it adds or changes a file — a live window into the work.
Naming & URL convention
The address is a random subdomain — the unguessable part is what grants access — with the artifact's
readable name in the path. In a chat UI the agent shows it as a titled link (“plan ↗”); in a
terminal it falls back to the bare URL, which still reads …/plan. Either way it's one click,
and you never type or copy a file path.
protocontent = proto (prototype)
+ content — the *.usercontent.com pattern every platform has, but for the ephemeral
stuff agents make.
Principles & non-goals