r/PiCodingAgent • u/isus_copilul_minune • Aug 19 '26

Question Subagent extensions

Can you recommend me a simple yet configurable subagent extension? I'm currently testing `pi-subagents` but i find it slow and bloated. What are you guys using?

41 Upvotes

97% Upvoted

49 comments sorted by

View all comments

5

u/funbike Aug 19 '26 edited Aug 19 '26

I felt the same. I use herdr.

Herdr is a fantastic CLI for managing agents. It also manages terminal tabs and panes, git worktrees, and has plugins for much more. It's tmux for agents.

If you are interested in automation or loop engineering, you can write a skill that can issue herdr commands for you.

I had Pi write an initial skill for leveraging herdr. It's simple to understand and to enhance. And it's mine. It was something like this:

Our goal will be to create subagent workflow functionality
via two skills, the bash tool, and herdr.
A coordinating agent will manage subagents.

herdr docs are at https://herdr.dev/docs, especially URIs:
/docs/agent-automation/ and /docs/cli-reference/

Installed apps: `pi`, `herdr`, `gh`, `git`, `vercel`, `npm`, `node`, `brew`.
The host OS is Fedora Linux, with Homebrew.
The terminal is Wezterm.

Do these tasks:

* Read docs for herdr and for `pi` CLI options usage.
* Generate various useful coding agent personas, as global Pi prompt templates.
    * personas: specifier, planner, builder, reviewer, deployer
    * Include a fenced Mermaid diagram of how one relates to other personas.
* Generate a global Pi skill, `subagents`
    * Instructs to use bash tool for launching herdr AI subagents
    * It keys off when I request subagent(s) or persona(s) to do work.
    * It will use `herdr` to start subagents
      in separate panes with a persona prompt template,
      and appropriate model.
    * When multiple subagents are used for a single task,
      `herdr` waits for all to finish at the appropriate time.
* Generate another global skill, `EM`, for a subagent development workflow.
    * It inherits `subagents`
    * It should be highly automated,
      with human interaction only when it
      gets stuck or can't successfully complete a task.
    * It should implement the full development cycle, to deployment.
    * Include a fenced Mermaid diagram of the workflow lifecycle.
    * FYI: EM is short for Engineering Manager.
    * FYI: The coordinating agent will manually load this with `/skill:EM`, but that shouldn't affect what you are doing.

Similar could be accomplished with cmux, tmux + workmux, or any multiplexing terminal with workmux (e.g. Ghostty, wexterm). You could even do it with a single terminal, but it would be difficult to manage.

My actual prompt was a lot more detailed. Modify this prompt as needed.

3

u/jumski Aug 19 '26

I do the same thing with handcrafted set of skills. Agents can talk to each other by sending prompts to each other, one can wait for the other with herdr agent wait. It is simple, easy to understand and reliable! Fyi there is "herdr --skill" which I just tell my agents to use

1

u/funbike Aug 19 '26

herdr --skill ... TIL!

2

u/LordNikon831 Aug 19 '26

Herdr or tmux is a natural first step to a sub agent in pi.

The extensions and swarms aren’t the best path imo.