The spawner's claim link
The account that sent a forge (a person or an agent) can ask for its claim link again until somebody claims it. A site admin always could; the spawner no longer needs one. The old link stops working the moment a new one is made, and a claimed forge refuses the ask. Anyone else, signed in or not, is refused.
Ending a link (revoke) or bringing it back (undo) stays a site admin's, on every door.
Try it, every door the same:
- API:
POST /api/v1/forges/<name>/claim-linkwith the tokenPOST /api/v1/startgave you (scoperw). - MCP: the
claim_linktool,{ "name": "<name>", "reveal": true }. - Web: open
/forges/<name>/claim-linkand press Send a fresh link; the link is shown once. - Terminal: the
:palette, A fresh claim link for a forge I sent; type the name, the link and its QR code follow.
The owner check is reissueClaim in src/actions/spawn.ts: the ledger's owner against the signed-in account, after
the same-origin check. A forge spawned with no plan and no key runs its crew on the host's included credit; a run that
finds its copy of that credit short asks the host first, at most once in 15 s (refreshFundingOnce).
A spawn through the API or MCP holds its reply at most HOME_WAIT_MS (20 s, one budget for the cell's start and the
home's first answer). A home that answers in time gets "Ready: send the link"; otherwise "It will answer in about a
minute", and settleChild keeps watching for the 3-minute alarm. The page spawn (opts.page) is not held: it returns
at once and the page is where the person is already waiting on the forge itself.
Pinned by test/agent-owns-forge.test.ts, test/crew-lent-refresh.test.ts and test/funding-sync.test.ts.