The page that answers "make me a forge"

What a person sees after pressing Start my forge (on /, POST /forges/start) or Spawn on /forges/new (POST /forges/new): one page, madeBody in src/web/forge_made.ts, in a no-store body. There is one answer, with or without JavaScript.

real step read from GET /forges/<name>/ready (forge-ready): "<name> is made and is starting. This usually takes about 15 seconds.", then "<name> is running. Checking that its address answers.", then "<name> is ready." Past a minute it says the start is taking longer than usual and keeps asking. The page asks again a quarter of a second after each answer, so the wait past the forge's own start is never seconds.

page: true: it answers as soon as the forge is made, and the proof of its public addresses (src/spawn/reach.ts) goes on behind it, an alarm if it never comes. POST /api/v1/forges and the MCP spawn still answer with the proof.

shown the moment the forge answers; on a phone the page opens it by itself. The link goes to the forge's /welcome (welcome).

Copy the link as the one primary action.

src/design/qr.ts), the link as text, and a way to copy it. The page says plainly that whoever holds the link owns the forge, once, for a day. The code is not drawn under 720px: the person is already on the phone.

prints it, with its own QR code.

Tests: test/stranger-three-screens.test.ts, test/new-forge-language.test.ts.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs