The French Brigade layer for agentic coding.
Run T3 Code in our open-source layer, work The Pass like a Chef de Cuisine, and let your agents cook.
Runs on your T3 Code account. Keeps no keys of its own. See why
We kept missing what our agents asked us.
Running ten agents in T3 Code is easy. Keeping up with them was the hard part. We tried three fixes before we built Yes Chef.
- A coordinator thread. We ran an air traffic control thread to route the work. It became a feed of status updates, and the questions that needed us scrolled past.
- Agents grading their own work. We let agents review, fix and merge in a loop. Some of it reached production without the final look it needed.
- T3 Code’s inbox. We hid working and settled threads. It still filled faster than we could clear it, and rulings got lost or backed up.
French kitchens solved agentic coding a long time ago.
A great kitchen turns out creative, exacting work night after night, at volume, without it slipping. Escoffier’s brigade is how: every cook owns a station, every order is a ticket, and the Chef stays at the pass, where every plate is checked before it goes out. Yes Chef runs your agents the same way, on top of T3 Code.
You only see work that’s ready for you.
The line cooks in parallel and you don’t watch it. When a ticket needs you, it lands at the pass with the plate, the checks and the pull request attached. You send it out, or refire it with a note.
Try it. You’re the Chef.
Tickets move through six stages, Order to Sent. Finished work waits at Plating for your call. Click any ticket to see what the agent made.
Our coordinator threads ate 19% of our tokens.
Our air traffic control threads kept every ticket in their own context and ran to almost 1M tokens. Yes Chef keeps that on the board instead. We replayed our last 30 days of T3 Code usage with Yes Chef in their place. The replay used 19% fewer tokens, or 14% fewer if you already run auto-compaction.
| Scenario | Claude | Codex | Total | Estimated cost | Change from actual |
|---|---|---|---|---|---|
| Actual | 35.63B | 2.97B | 38.6B | about $12.3k | none |
| Auto Compact | 17.77B | 2.41B | 20.2B | about $8.3k | −48% |
| Yes Chef > ATC | 28.74B | 2.60B | 31.3B | about $10.5k | −19% |
| Both | 15.14B | 2.13B | 17.3B | about $7.4k | −55% |
Total processed tokens, Oct 8 to Nov 7. Bar scale 0 to 40B. Auto Compact caps Claude and Codex at 300k. Yes Chef > ATC removes all 12 ATC threads (7.26B).
These numbers are modeled from our logs, not measured, and yours will depend on how you work. Both assume a short-lived expo thread that starts fresh from the board. Keep one open all day like our old ATC threads and you save 3% or less.
Yes Chef runs on top of T3 Code.
T3 Code runs the agents: Claude Code, Codex, Cursor, Grok, OpenCode and Antigravity. Yes Chef signs in to it and runs them as a brigade.
You stay at the pass. Each ticket arrives with everything you need to rule. You send it out or refire it from there.
Each agent works its ticket in its own T3 Code thread, one piece of work at a time.
One list of everything waiting on you: questions and finished work, oldest first.
- OrderNo brief yet. It is on the board.
- PrepBrief locked. An agent is assigned.
- FireAgents building: commits, a draft PR, checks running or red.
- TastingIn review. The PR is ready and your reviewers run.
- PlatingYour look. You call Go, Refire or Hold.
- SentThe PR merged.
How you run the Pass
Sign in with T3 Code.
T3 Connect opens. You approve Yes Chef in T3 Code and choose what it may do, from read only to full access. Your sign-in is the only credential Yes Chef holds, and you can revoke it in T3 Code.
Your threads become tickets.
Your T3 Code projects show up on The Pass. A thread is a ticket, its subagents are its stations, and its pull requests set the stage. A thread with a question waiting lands at the pass.
Every action goes back to T3 Code.
An answer, a Go, a refire, a hold: each one is a T3 Code call, capped by the access you granted. T3 Code runs the agents. Yes Chef shows you the line and carries your calls.
Any agent T3 Code runs gets a station. Yes Chef adds no agents of its own.
You stop babysitting threads.
The Pass only shows what needs you. Everything else keeps cooking on the board.
- APP-118, fire.Heard, Chef.
- APP-112 walking in.Chef!
- Triple check APP-109: the empty state.Heard, Chef.
- Hold APP-104.Hold, Chef.
- APP-108, go.Yes, Chef.
- No tab-hopping. An agent that needs you shows up at the pass. The rest stay out of your way.
- Everything in one card. The PR, the screenshots and the checks arrive together.
- Nothing merges without your Go. If it needs your look, it waits for you.
