Repository navigation
Roles & models: set the model for each kind of delegated work once (fork you can try) #38477
0xBreadguy
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The problem
Tired of naming the same subagent model every time you hand off a certain kind of task? I was. Today the options are saying it in every prompt or keeping a routing table in AGENTS.md that the agent copies into each
delegate_taskcall. #15182 and #33650 ask for this from two different angles.What I built
I built it as Roles & models on a fork, so there's something real to try and argue about instead of a mockup.
Settings → Threads → Roles & models has eight roles: architecture, implementation, research, review, security, design, test and general. Each one gets:
You set roles for the whole environment, and a project can override any of it.
The preview’s Roles & models screen with an example lineup. These are personal choices, not required models. “Always” is guidance to the agent; it is not enforced by the server.
How it behaves:
delegate_taskwith that role. The child runs on the role's model with the role's instructions. So a quick review can run on a cheap, fast model while a security pass gets a strong one.Try it
Unofficial preview builds for Linux and Apple silicon Macs are on the fork's releases. It installs as its own app, "T3 Code Roles Preview", with its own data folder, so your normal T3 Code threads and settings aren't touched. The code is on the
roles-previewbranch and the guide is Roles and models.Known gaps:
For scale, the feature is roughly 2.5k lines of app code plus 3k lines of tests and evals.
What I'm asking
I know CONTRIBUTING closes feature PRs from outside the team, so this isn't me lining one up. I want to know whether something like this belongs in T3 Code, and if it does, what shape it should take: settings like these, AGENTS.md conventions, or something narrower like the single subagent default in #33650. If it's wanted, the code is there to use or to learn from.
Reasons it shouldn't be adopted are as useful as reasons it should. If you've tried the preview, tell me what worked and what got in the way. Bugs in the preview itself go in the fork's issues, so this thread can stay on whether and how.
All reactions