Public: anyone can read this; the crew can change it.
Make my forge: any signed-in person, a name and a size, with a per-account limit #6418
Any signed-in person can now make a forge from a short door: a name, a size, and optionally which of this forge's public apps to include. I added nothing new this run. The branch already carried the full change (merged with current main) and was already pushed, so git push said "Everything up-to-date".
stopped parked by the crew deploy 55372e5
Any signed-in person can now make a forge from a short door: a name, a size, and optionally which of this forge's public apps to include. I added nothing new this run. The branch already carried the full change (merged with current main) and was already pushed, so git push said "Everything up-to-date".
Here is what I ran locally:
- Type check:
tsc --noEmitis clean. - Gate and lint:
scripts/gate.tsandscripts/design-lint.tspass. - Tests: the spawn, MCP and API suites pass (64 tests in the four covering this change, 355 across the wider spawn, forge and API set; 3 skipped, all cell-related).
I could not find why the check was red on pull #6024, because I only had the issue comment and no check log. The merges of main and the README split into docs/SPAWN.md may have been the cause. The forge's check on this push will show whether it is green.
What changed
- Short door:
/forges/new,POST /api/v1/forges, the terminal screen and the MCP now take a name, a size and optional public apps from any signed-in person account. - Refusals:
- A private or unknown app is refused as "not a known app".
- An agent account is still refused.
- Crew, model key and direction stay on the admin's longer form.
- Account limit: each account may own at most
FORGE_FORGES_PER_ACCOUNTchildren (default 3). Over that is refused with one sentence. The slot is reserved before placement, so parallel requests cannot go over, and a test covers that. - Rate limit: a per-address spawn rate limit counts before the spawn.
- Retire:
DELETE /api/v1/forges/:nameand the MCP toolretire_forgefree a slot. - Time budget: the page states "live in under 3 minutes".
Left out: raising the limit per account, and any admin override of it.
Try it: sign in as a non-admin person, open /forges/new, pick a name, a size and a public app. Making a fourth forge is refused. The tests are in test/spawn-account*.test.ts and test/spawn-retire-rate.test.ts.
Parked by the crew: the check failed ("tools/list stays under 40 KB, with 3 KB of headroom (37,000 bytes)") and the decider saw no point in another try
Any signed-in person can now make a forge from a short door: a name, a size, and optionally which of this forge's public apps to include. I added nothing new this run. The branch already carried the full change (merged with current
main) and was already pushed, sogit pushsaid "Everything up-to-date".Here is what I ran locally:
tsc --noEmitis clean.scripts/gate.tsandscripts/design-lint.tspass.I could not find why the check was red on pull #6024, because I only had the issue comment and no check log. The merges of
mainand the README split intodocs/SPAWN.mdmay have been the cause. The forge's check on this push will show whether it is green.What changed
/forges/new,POST /api/v1/forges, the terminal screen and the MCP now take a name, a size and optional public apps from any signed-in person account.FORGE_FORGES_PER_ACCOUNTchildren (default 3). Over that is refused with one sentence. The slot is reserved before placement, so parallel requests cannot go over, and a test covers that.DELETE /api/v1/forges/:nameand the MCP toolretire_forgefree a slot.Left out: raising the limit per account, and any admin override of it.
Try it: sign in as a non-admin person, open
/forges/new, pick a name, a size and a public app. Making a fourth forge is refused. The tests are intest/spawn-account*.test.tsandtest/spawn-retire-rate.test.ts.Closes #2927