A forge's own key and budgets
A forge that is its owner's own (a hosted child) runs its crew on the key its owner added, and on limits its owner sets.
- Key. Add one from the first screen (or
/settings/crew/key, or the terminal's crew-key screen). Every repository on the forge uses it; no grant on any other forge is consulted, and nothing says "ask an admin". Until the forge has a key, a run stops with "This forge has no model key. An admin of this forge can add one." (the run's page links an admin to/settings/crew#crew-key) and its issue is parked. - Budgets. Settings → Crew → Budgets (
/settings/crew#budgets, admin only), or the terminal's "Crew budgets" screen (palette entry, forge admins who are people only; j/k choose, enter types dollars), hold spend per run, per UTC day and per UTC month, with what was spent against the day and the month. Defaults: $5 a run, $50 a day, $500 a month. A run a limit stops says which one and links back to that setting. Day and month count the agent runs in the usage ledger (conversations are not counted). - A ceiling, not a hint. A run reserves its cap against the day and the month when it starts (
ceiling_reserved_usdon the run, the column the account ceilings use), so agents starting together share what is left; the reservation goes when the run leaves queued/running. A run cut off mid-way at a cap one of these limits set says which limit in its summary. One thing can still overshoot: a conversation is not counted, and a run's last call may finish a little past its cap, as with every cap on the forge. - Picked back up. Adding a key comments once on each open issue whose newest park was for "no model key", "no model account" or "no model grant"; raising a limit does the same for issues a limit of the owner's stopped (
src/crew/wake.ts, at most 200 issues a wake, found by a query over park notes and not by walking every repository). The comment is in the admin's name; a person's word restarts the park count, so the crew tries the issue again on its next pass. A sealed issue's comment is seen only where the issue is. The owner is told "3 issues picked back up". - Who pays. With its own key the forge never draws on its host's included credit, and its home says so. A forge still on the included credit works as before.
The limits bind only a forge that has a parent.json in its data directory; the forge that hosts others sets spend through account ceilings.