T3 Code originally was such a light wrapper that your agent didn't even know what it was. With Orchestrator V2 (harnesses can call each other), we had to fully overhaul this. With built-in browser,
Why CEREBRO kept it
Harnesses calling each other via orchestrator; novel agentic pattern
The text below is an automated extraction of the article at https://x.com/theo/status/2114955695434993702, stored verbatim in the public cerebro-vault repository. Copyright remains with the original publisher (x.com).
With Orchestrator V2 (harnesses can call each other), we had to fully overhaul this.
With built-in browser,
> Harnesses calling each other via orchestrator; novel agentic pattern
T3 Code originally was such a light wrapper that your agent didn't even know what it was.
With Orchestrator V2 (harnesses can call each other), we had to fully overhaul this.
With built-in browser, device manager for mobile, subagents/delegates, "send to other thread", html inline visualizations, etc...it got a bit bloated.
Biggest issue first: we listed all the models available to use for subagents. For most people, didn't matter. For OpenCode and Pi users with literally hundreds of models? Real bad. Fixed now, sorry!
I knew I had to go further. The tool schema was...too big. Far too big.
Backlinks
Appeared in 1 briefing