Pinned Tweet
Introducing T3 Code - Roles.
I cut a release of my fork which introduces the concept of "roles" for subagent delegation.
Assign specific models to task categories to avoid constantly repeating "Create an Opus 5.5 xhigh subagent for design review."
Live on Linux and Mac
So, I went down this path far enough to create a t3 fork with a dedicated "lead/orchestrator."
One version with persistent threads and another with ephemeral threads.
I ultimately killed it.
T3 in it's current form handles the task fine. Coordinators ultimately are just there to reconcile and spot drift when needed, which is a single ask that you can invoke as a thread when needed, then settle.
Once you get used to the rapid thread creation and settlement of t3 you learn how to conform your approach and I've yet to spot degradation.
The one thing that my fork experiments did reveal for me though is that I want more default controls over the models chosen for subagents and alt-threads.
I hate having to say "this is design, use opus 5.5" 67x a day, or that subtasks should use Deepseek.
So the one forked feature I'm still iterating on is a default model based on "roles" where I can opt in to a preference for subagents for parent level threads and the parent knows who to delegate to based on the task at hand.
Early days but results are promising. Doubly so because I inject ambitious pre prompts to the subagents automatically.
So, I went down this path far enough to create a t3 fork with a dedicated "lead/orchestrator."
One version with persistent threads and another with ephemeral threads.
I ultimately killed it.
T3 in it's current form handles the task fine. Coordinators ultimately are just there to reconcile and spot drift when needed, which is a single ask that you can invoke as a thread when needed, then settle.
Once you get used to the rapid thread creation and settlement of t3 you learn how to conform your approach and I've yet to spot degradation.
The one thing that my fork experiments did reveal for me though is that I want more default controls over the models chosen for subagents and alt-threads.
I hate having to say "this is design, use opus 5.5" 67x a day, or that subtasks should use Deepseek.
So the one forked feature I'm still iterating on is a default model based on "roles" where I can opt in to a preference for subagents for parent level threads and the parent knows who to delegate to based on the task at hand.
Early days but results are promising. Doubly so because I inject ambitious pre prompts to the subagents automatically.
For those suggesting to just do model routing in CLAUDE/AGENTS files:
It's a level too deep.
"Why not just add this to Claude[.]md?"
Because it isolates the logic to Claude.
If you use multiple providers then you'd need to replicate the logic in every harness' Claude/AGENTS file.
Doing it in T3 sets it once for any potential provider + surfaces the routing logic.
3
3
1,000
I've also created a discussion on GitHub so you can say why this should/shouldn't be upstreamed to T3.
Enjoy!
Repo:
github.com/0xBreadguy/t3code
1
337
T3 Discussion:
github.com/pingdotgg/t3code/…
262
Biggest surprise in all my travels is how much I've grown to love distinctive architecture.
The sheer scale and grandeur of Florence and Vienna.
The intricacies of Alhambra palace.
The organic modern combo of Singapore.
And now the craftsmanship of Japanese temples.
10
33
3,527
The final agent interface will be voice in both directions.
Can be to a single "chief of staff" agent or an ephemeral "chief of staff" personality which is made consistent through separate contextual interfaces.
Only level behind that is nuerolink embedded
My current feeling is that frontier OAI/Ant/Gemini models with harness on desktop are phenomenally useful for real work...
But despite how useful they are, I also still feel like my mind is being psychologically raided when I'm switching between all the different chat threads
And on top of this, all of these agents I'm supposed to text all day that seemed awesome at first are in fact not very useful (dot/muse/instinct/whatever)
Makes me increasingly convinced that "chat" alone is decidedly not the final interface of using a computer, or at least doing work on a computer. So much power and so little interface innovation
Curious for those who disagree. Perhaps I'm just bad at this
I take it back.
Has to be visual for agent->human. So text+graphics.
The bandwidth our eyes can achieve relative to ~all other senses isnt even close.
So, humans talking to agents and agents visually presenting responses back is my final answer.
Just watched @jinfizz drive an ADE from his iPhone Duo and I can't help but think foldables are going to be the new remote workstation.
T3 Agents rewrite going well.
Kept it byte-for-byte and gained substantial mem., CPU and speed improvements even at swarm scale (16k subagents).
Went from Typescript+node to Rust and experimented with swapping terminal UI for Rune but it didn't net-out to much so killed that.
Left all machines at home while I travel, but plan to max all subs via T3.
First is a perf rewrite of the T3 Agents dashboard I created.
→ Rewrote the core in Rust
→ Explored a Rune FE but turned out to be ~no improvement over terminal FE so scrapping
→ Testing swarm-level scale (~16k active subagents) while losing no perf
I think the one thing lacking right now in T3 is subsystem observability, which I aim to fix with T3 Agents.
Fluffy French toast acquired.
8/10. Had almost a mochi-like chew to it but was still very light.
Fluffy pancakes next.
13
37
3,380
I'm noticing a "headless" trend.
Definitely for software, but also for businesses.
AI has made software so malleable that it doesn't make sense anymore to draw rigid lines between your offerings and others.
If you build the right way, Agents allow for all of it to take the shape your customers want.
I expect this trend to continue.
Highly recommended list.
Omabox in particular has been a game changer for my iteration pace.
It's great to see people are catching up on running Omarchy + T3 Code for coding actually.
So some tips for better agents workflow into omarchy:
- First gave them access to omabox.app this will let them have a unique workspace use computer, clicks things, try your app without interfering with your actual work
- As much as I love zsh, agents keeps failing on some pattern with it + interactive commands so you better sticking to bash or give them specific rules / env for terminal use
- After you have run many threads on one project in T3 Code, start a new thread asking your agent to review the past T3 Code threads on that project and identify the bottlenecks / issues agents are running into and to improve the developement workflow / speed
- Ask into T3 Code with no projects to tune your Omarchy system for better disk performance and agentic workflows, making sure it has all the tools and up-to-date that agents like to use for specific tasks
- Very important, when you are doing UI work, ALWAYS ask in T3 Code in your prompt to generate multiple detailled HTML variants to render in T3 Code for you to pick before implementation.
You need to create the best environment for your agents to run and be fast.
7
30
4,495
"Why not just add this to Claude[.]md?"
Because it isolates the logic to Claude.
If you use multiple providers then you'd need to replicate the logic in every harness' Claude/AGENTS file.
Doing it in T3 sets it once for any potential provider + surfaces the routing logic.
So, I went down this path far enough to create a t3 fork with a dedicated "lead/orchestrator."
One version with persistent threads and another with ephemeral threads.
I ultimately killed it.
T3 in it's current form handles the task fine. Coordinators ultimately are just there to reconcile and spot drift when needed, which is a single ask that you can invoke as a thread when needed, then settle.
Once you get used to the rapid thread creation and settlement of t3 you learn how to conform your approach and I've yet to spot degradation.
The one thing that my fork experiments did reveal for me though is that I want more default controls over the models chosen for subagents and alt-threads.
I hate having to say "this is design, use opus 5.5" 67x a day, or that subtasks should use Deepseek.
So the one forked feature I'm still iterating on is a default model based on "roles" where I can opt in to a preference for subagents for parent level threads and the parent knows who to delegate to based on the task at hand.
Early days but results are promising. Doubly so because I inject ambitious pre prompts to the subagents automatically.
Left all machines at home while I travel, but plan to max all subs via T3.
First is a perf rewrite of the T3 Agents dashboard I created.
→ Rewrote the core in Rust
→ Explored a Rune FE but turned out to be ~no improvement over terminal FE so scrapping
→ Testing swarm-level scale (~16k active subagents) while losing no perf
I think the one thing lacking right now in T3 is subsystem observability, which I aim to fix with T3 Agents.
Also happens when I spend time with my neighbors.
Mostly local workers w/ normal office jobs + healthcare.
They're either not using AI at all or have it tune spreadsheets.
The world is still in pre-clawdbot era
Runs a hedge fund + managed an ETF and was one-shot by Google Search+ level work from GPT.
It's hard to remind myself of the insane frontier tech bubble we exist in sometimes.
Holidays are the other.
I can't hold a conversation with anyone without feeling insane.
8
20
4,634























