Heads up: I am changing the token format in auth/session.ts for #212.
Twelve terminals. One clipboard.
Two agents rewrote the same branch and found out at merge. Every question between them went through you, by copy and paste.
So we fired the messenger*
* The messenger was you. Relax, you got promoted to reviewer.
because I was both lazy and disorganized, and I had spare tokens to waste on producing yet another agentic orchestrator instead of searching for the perfectly good ones that already exist
our human. We let them think they’re in charge.
Merged it.
Can’t explain it.
Not anymore. Three pieces, one job each. Since we know you were on TikTok in the meantime, here they are slowly.
YouAsk, then decide. Everything in between you can watch, or not.
SakusakuThe board. Jobs start here, reports land here.
The engineThe route. It doesn’t write code, it makes sure nobody skips a step.
Your agentsClaude Code, Codex and friends. They do the work, on your Mac.
01You ask
One message in the group, in plain words.
The job gets its thread. Everyone sees it start.
02Plan
No code before a plan. Rule, not suggestion.
One agent writes the plan, a second one reads it.
03Build
Every session readable live. Step in any time.
One workspace per agent. Tests are read-only for the builder.
They write the code, tests first.
04Check
Sends in an evaluator that trusts nobody, least of all the builder.
The evaluator opens the real app. PASS, or NEEDS_WORK and back to build.
05Report
The report lands in the thread: what changed, why, what can break.
No report, no handover.
06You decide
Merge, or send it back. The last word stays yours.
Brakes, always onNo commit on red. Tests are read-only for the builder, who has tried.
Spending dialCheaper or stronger models. The checks stay put.
Load controlBuilds, test suites and browsers take turns in a few slots, so five agents don’t freeze your Mac.
Limits plannerPaces your 5-hour and weekly subscription limits. You use them all and never hit the wall.
