A couple of weeks ago, I shared Pi Herdsman here, an extension I've been building to connect independent Pi sessions through Herdr.

At the time, I mentioned wanting to take the Herdr integration further, particularly around spaces, tabs, and project-level coordination.

Quite a bit of that is now implemented, so I wanted to share an update with an actual recording of Pi, Herdr, and Herdsman working together.

What's happening in the video?

I give a Manager one prompt to implement two independent features for a fictional note-taking application.

The Manager delegates both features in parallel:

• Each feature gets its own Lead and Git worktree.
• Each Lead delegates implementation to its own Agent.
• The Leads verify the changes, commit their work, and report back to the Manager.

Herdr organizes the sessions into its native workspace, tab, and pane structure. Placement is configurable, and every session remains directly accessible.

That's one of the things I particularly like about this setup. Even when the agents are coordinating automatically, they're still ordinary Pi sessions that I can switch to, inspect, or interact with whenever I want.

The responsibilities remain separate:

• Herdr manages sessions, processes, panes, workspaces, and placement.
• Pi manages the actual coding-agent conversations.
• Herdsman manages delegation, ownership, lifecycle, and coordination.

Still usable for simpler workflows

The more advanced orchestration is optional.

You can still work in a normal Pi session and occasionally delegate something to a background Agent without setting up a Manager or separate projects.

There are also configurable Agent Definitions for each role, so different Leads and Agents can use different models, tools, instructions, skills, and extensions.

Try it

If you already have Pi and Herdr installed:

pi install npm:pi-herdsman
herdr integration install pi

Repository: https://github.com/boadij/pi-herdsman

Thanks to everyone who shared feedback after the original post. Some of the suggestions around Herdr's higher-level organization helped shape this direction.

I'd especially be interested in feedback from people using Herdr with multiple projects or worktrees. How would you want the sessions and workspace hierarchy organized?