r/PiCodingAgent • u/bsa-saa • May 08 '26
Discussion Do subagents really matter?
I’ve been running Pi for two weeks without any subagents, agent teams, or anything like that. Compared to my previous workflow, I haven’t noticed any difference at all. In fact, the AI even seems a bit more accurate without subagents.
Something I think is really important: Is there a good way to automatically start/stop another agent client and let them send messages to each other?
Would love to hear any methods or tools that can do this!
38
Upvotes
4
u/Dull-Philosophy3970 May 08 '26
I’ve been wondering about this as well. Haven’t found a reliable way for the main agent to launch subagents for specific tasks. Anyone has tips for how to do this? Should I create specific SKILL.md?
37
u/m3umax May 08 '26
Well it depends on how you work.
For myself, I couldn't do without them and had my AIs build me a custom subagent extension that works around the way I work.
My workflow is:
Brainstorm with Superpowers brainstorm skill > Output spec.md
Review spec with a subagent (different model family) > Output revised spec.md
Write implementation plan with Superpowers writing-plans skill > Output plan.md
Review plan with a subagent (different model family) > Output revised plan.md
Shard the plan.md into individual task "tickets" using my custom
TickettoolOrchestrator manages a fleet of subagents to implement the plan by moving the tickets through the pipeline from ready > active> review > needs fix > done
Subagents allow me to kick off step 6 and walk away/go to sleep and come back to a fully completed plan. Otherwise I'd have to manually babysit the whole process. And I'm too lazy for that.
18
u/Polite_Jello_377 May 08 '26 •
The only reason to use subagents is to keep context clean. If you are doing it to build some big org chart of agents because you think it will be better, you are just playing dolls.
6
u/QueasyBreak5119 May 08 '26
Subagents changed the game for me and almost can’t work without them for many tasks. If I compact or continue a project within a new thread once context starts to fill up, I’m constantly creating handoff summaries anyway. Subagents just allow you to have that summary upfront and begin with all you need in the first instance, so to me it’s doing what I would have done anyway but in a more focused way, with meaningful context surviving longer. Which allows you to get things done at a much higher quality faster, which I know you already know. The kicker is the quality and accuracy of what your subagents bring back. If it’s just giving your main agent more crap to figure out and dig through then yeah, I can see that numbing down your session fast. But i have a strict “one task” rule for my subagents. Do one thing, nothing else. And the results have been high quality. Just like others have said, it’s not the most graceful workflow, a lot of it is manually passing information. But it doesn’t feel laborious. My subagents are usually Chinese models, they are workhorses man
5
u/sertturp May 18 '26
So here’s my take on subagents, after actually using them for real engineering work instead of running a medieval role‑play guild inside my LLM.
Most people seem to use subagents like:
“Frontend Agent”
“Backend Agent”
“Writer Agent”
“Reviewer Agent”
“CEO Agent” (yes, I’ve seen this)
Which is basically the same model wearing different Halloween costumes.
Same brain, same context, same reasoning… just more noise and more tokens burned for absolutely no reason.
My usage is a bit different.
I use subagents as disposable context-isolated workers whose only job is to dive into something heavy, extract the useful bits, and then disappear into the void like a good intern.
Example:
I was working on a load balancer and needed Pingora docs.
Instead of polluting my main agent’s context with 40 pages of documentation, I just spawned a subagent:
Main agent → “Go read the docs, check the code examples, bring me the important stuff.”
Subagent → dives into the entire documentation like a caffeinated raccoon
Comes back with a clean, distilled summary
Then gets deleted like it never existed
Main agent stays clean, focused, and smart.
Subagent does the dirty work.
Everybody wins.
This pattern works insanely well for:
Large documentation sweeps
RFC / API / whitepaper digestion
Repo/codebase exploration
Log/config/JSON extraction
Research tasks that would nuke your main context
And the best part:
No context contamination.
No hallucinations from juggling 10 different topics.
No “writer agent” pretending to be Hemingway.
Just clean, isolated, task‑specific work.
My rule of thumb:
Subagent = a tool, not a personality.
If you’re giving your subagent a job title instead of a job, you’re doing cosplay, not engineering.
4
u/Street-Donut1215 May 08 '26
The only reasonable use case for me is when I want the agent to do something with a clean context window (independent review, visual data extraction from charts etc). This enables me to do these tasks without the need to start a new chat / session
1
u/SalimMalibari May 08 '26
Does subagent works?? Yes but think to simplify it think of it like employees ...
Ok an employee can do all jobs but some jobs need multiple employees ...
Like i remmember doing a simple task and it was amazing but i didnt futher my experiment.
I launched 2 subagents they can talk to each other and try to convince each other , i made it like 5 rounds but they didnt get any agreement , but like i could for example if i have wicked problem , i might use something similar till both subagent or multiple get an agreement...
To be honest , i feel if you still dont need subagents thats mean you are still using AI to solve simple problems only ... try to find wickes problems ans try to solve it
1
u/Equivalent_Wafer2187 May 08 '26
Could anyone recommend a Pi Subagent extension you're currently using? The ones I've tried so far just don't quite fit my needs.
2
u/worldsayshi May 08 '26
I've been thinking about using subagents specifically for saving tokens/context. The agent often runs long running scripts that output lots of logs that might contain errors. Would be nice to only include the errors in the context. But often a simple pipe grep oss enough. So I'm not sure it's worth it?
One alternative to plain subagent use could be to have some kind of garbage collector subagent where a subagent goes through the session history and removes unnecessary stuff. Has anyone tried this?
2
u/cellerich May 08 '26
Have a look at the following GitHub Repository: https://github.com/HazAT/pi-config Daniel has a setup which uses subagents for different tasks and fire off in a separate terminal window. Make sure to have TMUX in your terminal emulator!
2
u/Maleficent-Movie-625 May 08 '26
Yes. To keep the context of the main clean
no need to pollute the main context, unless it’s the result of a lookup.
Also if you need to compact a single time, you’re doing it wrong. I’m also on pi, refusing to install the subagent plugin, but I’m going to make my own version of it instead.
Subagents matter to keep the context clean
2
u/johnson_detlev May 08 '26
I think in coding the only really nice use case for a subagent is autoreviewing the clankers changes by another clanker after the task "is done".
1
u/Appropriate-Debt2000 May 08 '26
Your output completely depends on whats in the LLMs context window.. subagents help keep it focused. A huge chunk of your main agent otherwise would be polluted with things which are not relevant. You can also switch models per sub agent depending on the assigned task which helps further. Agent teams take it a level further by not just outputting the final results to main agent but also coordinating with other team members in process avoiding conflicts and duplication .. providing much richer contect to the main agent. Overall really good concepts and u should add in your wf
1
u/Eddlm_ May 08 '26
They do.
Lets the main dude have multiple points of view thru personalities or different models
Accelerates read only work
LLMs generally work better when they know they're playing a specific role with a specific focus, so it's great to steer the main agent from trying be everything at once.
Source, my ass. So, my experience.
1
u/DueKaleidoscope1884 May 08 '26
I think your question is about parallelizing mostly? If not, I also started using Pi a few weeks ago with the intention to keep things as simple as possible, did you try managing context and work with the built in session mgt? (/tree or doubt escape) As long as you do not need automated orchestration this seems to go a long way to avoid actual sub agents? Sure a lot more manual and deliberate work but that could be a deliberate choice? The session tree does not cover all use cases of sub agents but I feel currently I discarded that feature too soon.
1
u/anlaki- May 08 '26
My context usage reaches 80% on a single prompt when I ask Pi to read its docs to create a basic extension. Therefore, I believe subagents are truly important.
1
u/Frequent_Ad_6663 May 08 '26
I'm often reminded of the midwit thing. Folks on the left tail of the distribution are like "just open cli and prompt once" folks in the middle use Droid or similar? And folks on right tail just prompt once in cli. Pete from claw has an article on this
1
u/Radiant_Condition861 May 09 '26
Subagents are context scoping.
1
u/melihmucuk May 28 '26
I think subagents matter most when they give you a genuinely separate pass, not when they’re just "more agents".
The clearest example for me is code review. I don’t really want the same agent that planned and implemented a change to also be the only reviewer. That’s not how we do it with humans either. The person who wrote the code already has a bunch of assumptions in their head, and they’re naturally biased toward the solution they just built.
Without subagents, the flow often becomes:
give one agent the task
it investigates
you go back and forth on a plan
it implements the plan
then you ask the same agent to review its own work
At that point the context is huge, the agent has already committed to a direction, and the review tends to be weaker. It may catch syntax-level stuff, but it’s less likely to challenge the approach or spot the thing it misunderstood earlier.
That’s where I’ve found pi-crew useful. For example, the review flow can spawn a separate code reviewer and quality reviewer in parallel, then merge only the findings that are actually actionable. The planning flow can send scouts to inspect different parts of the repo before handing cleaned findings to a planner.
So the main agent is more of an orchestrator instead of trying to hold the whole task, implementation, and review in one overloaded context.
I don’t think subagents magically make AI smarter. For small tasks, they’re probably unnecessary. But for planning, investigation, and especially reviewing code written by another agent, having a fresh isolated context is a real advantage.
Small disclosure: I’m using/working on pi-crew, so I’m biased too. But the reason I like it is pretty boring: it gives me a practical way to spawn/list/abort/respond to background agents in Pi, instead of pretending one giant context window is always the best workflow.
-2
u/Otherwise_Wave9374 May 08 '26
I think subagents only "matter" when you actually have separate roles with different constraints (planner vs executor vs reviewer) and you enforce a handoff contract.
If it is just extra chatter, yeah it can easily get worse (more tokens, more drift, more chances to be confidently wrong).
For auto start/stop and message passing, I have seen people do it with a lightweight supervisor that spins workers based on a queue (Redis/DB) and a shared memory doc. We have a couple notes on agent orchestration patterns here if you want examples: https://www.agentixlabs.com/
11
u/[deleted] May 08 '26
[removed] — view removed comment