Decisions
Four design questions were open before the first slice. The shipped code settles all four.
1. Isolation Decided
Section titled “1. Isolation ”Two options: one shared agent service for every User, or one Workspace for each User. Budi gives each Pro or Max User their own Workspace (a Tenki Volume) and a fresh session for each Run. Free Users have no Workspace: their Job search runs in a throwaway session.
2. Hermes Decided
Section titled “2. Hermes ”Claude Code runs every Run, headless, inside the session. Hermes is not in Budi’s path, and there is no separate agent service: the api starts the sessions itself.
3. Cost path Decided
Section titled “3. Cost path ”One model call per Evaluation would cost a few cents but could not use career-ops. Budi uses the full agent loop: career-ops driven by Claude Code on the User’s Workspace, with a dollar cap on each call. See Runs for the caps and the measured costs.
4. Files Decided
Section titled “4. Files ”The career files stay in the Workspace. Postgres keeps the records and R2 keeps the files the web shows. See Data.
Still open
Section titled “Still open”| Item | Status |
|---|---|
| A backup of each Workspace, which is the only copy of the career files | Open |
| More defenses against instructions planted in employer pages | Open |
| Max’s Quota numbers (“higher than Pro” is decided) | Open |
| Whether “Coach” names anything in Budi, and whether Agencies return | Open |