I'm really curious how folks feel about this. I regularly use subagents, but typically make my primary implementation agent use Carbon (or equivalent).
I set up my subagents with specific models based on how complex I believe the problem space is. I'm nervous to delegate that authority to a model (since models tend to be... optimistic about their capabilities.)
That said, not every coding task is a difficult coding task. Plenty are boilerplate, plumbing, or simple test authoring that could use a flash model, so maybe this would downgrade nicely.
On the other hand, it's trivial for me to set up some guidelines to create different subagents for different task domains, and just pin those models to those tasks -- implementor (hard) and implementor (easy) or whatever.
I'm really curious how folks feel about this. I regularly use subagents, but typically make my primary implementation agent use Carbon (or equivalent).
I set up my subagents with specific models based on how complex I believe the problem space is. I'm nervous to delegate that authority to a model (since models tend to be... optimistic about their capabilities.)
That said, not every coding task is a difficult coding task. Plenty are boilerplate, plumbing, or simple test authoring that could use a flash model, so maybe this would downgrade nicely.
On the other hand, it's trivial for me to set up some guidelines to create different subagents for different task domains, and just pin those models to those tasks -- implementor (hard) and implementor (easy) or whatever.
Excellent mode! I don't have to constantly switch between models and efforts.
Discussion on the front page (191 points, 121 comments) https://news.ycombinator.com/item?id=50471431
Not the same article, this one has orchestrator and some antigravity stuff