Skip to main content
Put what the agent built on a public URL, and share it. The agent starts a server in its workspace; you publish it; someone who has never heard of Gobare opens the link in a browser and sees the thing. This is the part that makes a session more than a job runner: the agent builds something, and the something is reachable. Preview and publish are two different addresses, and the difference is who can open them. preview.url opened in a browser shows the Console, not your app. It is scoped to a caller holding a token, and an anonymous request is not refused — it falls through to app.gobare.dev and answers 200 with the Console’s own page. So a reader who copies that address out of a session, pastes it into a tab and sees something that is plainly not what the agent built concludes the agent built nothing. published_url is the one to hand to anyone else, and it is null until you publish. That is the next section.

​
Requirements

Publishing exposes a port. The agent must have started a server on it and told the workspace about it — in the agent’s own words, preview(3000). Ask for it in the same sentence as the work:
When it has, the session says so:
port is the signal. Until it is set there is nothing to publish, and asking anyway is refused rather than answered with an address that returns errors — you would hand that address to someone before discovering it was empty.

​
Publishing

You may name it instead:
Left out, the name is derived from the session id. That is deliberate: an address you have to invent is an address you can lose a race for, and most callers want a URL to hand to something else rather than a name to remember. The reply is a Gobare origin, never the sandbox provider’s. That matters because the workspace behind it can be rebuilt and the address survives.

​
Sleeping and waking

Publishing grants a stable route, not a permanently running computer. An idle workspace is still paused on the usual schedule; the first public request wakes it. A visitor waits a few seconds, and then sees the site. So a published preview is not a hosting product, and it is not billed like one. It is the agent’s work, left reachable.

​
Unpublishing

The session and its workspace are untouched; only the public address goes. Publishing again afterwards is ordinary. Unpublishing something already unpublished answers 200 too, with the same body. A teardown that runs twice, or one racing a person doing it in the Console, has already got what it asked for — and the two answers are indistinguishable, which is what makes the retry safe. A session id that does not exist is still not_found; that refusal means something. Deleting the session removes the address too — see design-decisions.md on why DELETE destroys the workspace rather than archiving it.

​
Errors

Republishing to the address you already hold is not a conflict — it answers 200 with the same URL, because that is what a retry looks like. Unpublishing twice works the same way, for the same reason. Both routes honour Idempotency-Key like every other write — see idempotency.md. Every refusal on this page arrives in the shape described in errors.md; if you have a symptom rather than a code, start at troubleshooting.md.

​
Next