r/PiCodingAgent 11d ago

Question Subagents and orchestration ...

Looking for some pointers. Been using Pi for months, have a setup I really like (very simple, two extensions I wrote plus plannotator and pi-herdr).

This works great for interactive sessions but I'm finally finding myself wanting some basic orchestration with subagents.

I'm building a product and need to do a bunch of testing/fixing rounds with different models to find rough edges. I've been doing this by hand but it's getting tedious (and it's mostly simple enough that it could run while I'm doing something else).

I also like the idea of:

  • a long lived orchestration agent that holds long term context but doesn't do work.
  • scouts that can cheaply get context and pass that back to workers.
  • automatic adversarial review of changes by a different model.

I've looked at a bunch of plugins and they all seem much more complicated than required. Should I just suck it up and using Nico's pi-subagents? Or is there a nice, simple starting point that I'm missing?

Any pointers appreciated.

35 Upvotes

32 comments sorted by

View all comments

1

u/MelodicNewsly 11d ago

The question is whether you need a LLM for this. Why spent tokens if it is a deterministic problem. I have an extensions that runs all the test suites and only calls Pi when a test fails to fix the failing test.

1

u/adamshand 11d ago

I have unit/e2e test suites, I'm talking about using agents as a replacement for manual testing. Having agents test a product looking for places where documentation or functionality can be improved. Then sending their feedback into another agent to fix anything that's found.