Pinned post
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
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
0:36
So, I went down this path far enough to create a t3 fork with a dedicated "lead/orchestrator."View quoted post on X
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.