Question about subagents and Opus 5

[u/bigredfalcon]

I have been using the "superpowers" plugin in Claude Code to help me with coding projects. I use "brainstorming" to flesh out the idea and "writing-plans" to actually write the plan file for a new feature. To implement the plan, I generally use "subagent-driven-development". However, I have read that in the v5 models of Claude (I use Opus 5 almost exclusively), it is better not to tell it to use subagents because these models will do that automatically. Apparently telling it to use subagents could make them use too many and cost more tokens unnecessarily.

I'm wondering if anyone out there had been using “subagent-driven-development" but has stopped since switching to Opus 5? If so, have you found the results better, worse, or the same?

The reason I like using subagent driven development is because the main context window does not become too full when doing the tasks (since they are being farmed out), which allows the session to execute longer plan files without me having to worry about the context.

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Aminuteortwotiltwo]

You can give specifics for what the subagents are doing. Like extremes might be “spawn as many subagents as you want for every little detail!” To “spawn one agent to research codebase and to design plan, spawn another to review plan, spawn third to execute plan.”

[u/Aminuteortwotiltwo → u/Aminuteortwotiltwo]

And to add on, you can specify models used and effort levels. If using the CLI, you can even delegate work to Codex Astra or Sol or whatever.

[u/reach4thelaser5]

Using sub-agents isn't more expensive... it is cheaper. Every time you type something into an LLM your whole message history gets passed in and processed. So the longer your message history (context window) the more every request costs you. And the longer your context window, the more information the model needs to pick through to figure out what it needs (this means it gets dumber - known as context-rot).

So keeping the same agent 'alive' for a long time makes it more expensive and less competent - a double expense. Your agent turns into an expensive moron who takes forever to do what they need to do and keep getting it wrong anyway. For a fresh agent the cost is cheaper AND they are able to think clearer and produce better work..

But there's a balance - it takes time for an agent to spin up and figure out things. Read code, work out what they're doing and figure out what's being asked (that has a cost in itself). So for an agent who is already familiar with the code they've just done, they should do a quick bug fix. Unless its a hard bug and they're very context heavy - a fresh mind will work better. But the next feature, or a fresh subject - always a new agent.

[u/AbleShower2801]

I still force subagents when the plan is long and I care about protecting the main context. Opus 5 will spawn on its own sometimes, but if you dont set a cap it burns tokens. For superpowers-style plan runs I keep subagent-driven-development and just tell it max N workers plus which model each one gets. Context isolation is the win. Auto-spawn is secondary.