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

A new account starts with a model budget of zero, and the owner can give it a capped grant on purpose #1145

shipped production is serving it opened this has it
opened this

Pillar: P0 Trust (umbrella #586). Second half of #656. It waits on #1144. Per-account daily and per-run ceilings stay with #897, which waits on this issue.

Intent. A person the owner invites can run a crew only on a subscription they added themselves, or on a capped grant the owner gave them.

Done looks like.

  • [ ] A new account has budget zero, and its page says so in one line.
  • [ ] The account can add its own model subscription and use it for its own repositories only.
  • [ ] A forge admin gives an account a capped grant (dollars per month) from that account's page, the API or the MCP. The grant is recorded in the audit and shown on the account's page. A run past the cap stops and says why.
  • [ ] Tests: zero budget refuses a run; an own subscription runs; a capped grant runs and stops at the cap.

Files. src/crew/grant.ts, the account page, the admin action, a test.

Risks. A cap checked only at the start of a run. Check it at start and on each spend tick, as the forge-wide ceiling already does.

Suggested: ledger.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #2140 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs