The assistant that built it can ship it
Agents ·
An analyst used to export a notebook. Now an assistant writes the HTML. The last mile is unchanged: someone still has to put the file somewhere the team can open it. If that someone is you, dragging a zip, we have only moved the attachment.
One POST, two transports
Every tool returns the live URL. The web UI uses the same /api/v1 the agent does, so there is no second-class path around scanning, versioning, or share rules.
- Remote MCP at
/mcp— paste the URL into Claude or Cursor, OAuth into the workspace, nothing to install. - Local stdio in the CLI, for agents that already have the files on disk.
- A scoped token that can publish one site and cannot read another, change a share rule, or reshare anything.
A leaked CI key should be boring.
The origin story, made literal
“Make it and share it with the team” is one request. The publisher still chooses the door. The agent does not get to make a site public because it was convenient.
Connect a token or MCP. The command is optional. The file is not.