Public: anyone can read this; the crew can change it.

An agent deploys a forge for its person, and that forge scales to zero when idle #9444

Closed opened this has it

Landed in pull #9547 · run

opened this

The owner, 2026-11-06: "i would like them to be able to deploy forges that scale to zero", meaning the assistants people bring (ChatGPT, Claude, Grok) through /agents and the MCP connector.

Pieces that exist: child forges (/forges/new, the MCP spawn tool), hosted children answered in-process (src/spawn/host.ts), apps that sleep and wake, and the guest role and limits. Guests can't spawn today.

Done when:

2 earlier comments
commented

Reviewed pull #9547 at its head: ticked A person, or the agent acting for them over MCP with their consent, creates their own forge in one step from /agents: a name, and an address like <name>.forge.open-platform.sh or <name>--forges.open-platform.sh.; An idle forge costs nothing while asleep: its process stops after a quiet period, its state stays on disk (or in the bucket), and the first request wakes it within a few seconds with a plain "waking up" page instead of an error. Git pushes and API calls wake it too.; It never gets this forge's secrets or model credential. The person brings their own model credential, or the forge says the crew is off until they do. It runs contained like apps do.; The owner sees all hosted forges, their state, size and last activity, and can stop or remove one.; When hosting is sold, the same path takes payment. Until then it's free within the limits, and the page says so.; A test proves a forge sleeps, wakes on a page load and on a git push, and keeps its data across both.. left open: Limits per person: forges per account, storage, wake rate, and a forge-wide ceiling on how many run at once. Each refuses in plain words. A sleeping forge doesn't count against the running ceiling. — Forges per person, wake rate and the awake ceiling are done; per-person storage is not, only the existing per-child quotas..

commented

Left open after pull #9547 landed: 1 unticked item remains (Limits per person: forges per account, storage, wake rate, and a forge-wide ceiling on how many run at once. Each refuses in plain words. A sleeping forge doesn't count against the running ceiling.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split: the limits box is now #9581 (count and storage per person) and #9582 (wake rate and the running ceiling, where sleeping forges don't count).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs