Theo ships a T3 Code overhaul and warns it will break your nightly
A stable build was cut first, and daily drivers are told there is no shame in going back to it.
Theo merged a release into T3 Code that rewrites how the tool works, and he posted a warning before it landed. The next nightly build, he said, is a huge overhaul, and the team cut one more stable release before merging so that anyone who has been daily driving the nightly has somewhere to retreat to.
The full list he published is long. Pi support. Auto-resume when limits reset. Thread forking. The ability to switch provider or model in the middle of a thread. Scheduled tasks. Proper server-side queueing and steering. Native subagents that show up as child threads in a lineage view with their model, status and history. An ACP Registry that lets you add any registry agent, with Devin, Cline, Kimi and Droid named as examples. Cursor now runs on the official Cursor SDK rather than what Theo calls the broken CLI. OpenCode 2 support. Agents can rename threads, regenerate titles, link PRs and settle threads. You can type an `@` with a thread name, or drag a thread from the sidebar, to attach it as context.
`delegate_task` lets an agent start child agents on any provider or model
He expects days of cleanup to get it right.
The piece worth watching
Buried in that list is `delegate_task`, which lets an agent start child agents on any provider or model. Alongside mid-thread provider switching, that means one conversation can hand work to several different vendors without you leaving it. There is also a T3 Code MCP that can create, launch, message, wait on, read, search and interrupt threads, which makes the tool something other agents can drive rather than only a thing you sit in front of.
The business read is that the orchestration layer is where the fight is. If the thread can fork, switch model mid-flight and spawn children on whatever provider is cheapest or best right now, the model stops being the thing you are locked into and the harness becomes it. Theo is building the harness.
For anyone already running the nightly in real work, the practical advice is in his own post. He knows a lot of people have had an overall stable experience on it, and he is telling them plainly that this one will not feel that way for a while. T3 Code passed 400,000 users earlier this month, so the pool of people who can get bitten is not small.
Nobody has independent numbers on how any of this performs yet. What exists is a merged pull request, a feature list from the person who shipped it, and a warning attached to the front of it.
This release is gonna feel more "nightly" for sure.