r/herdr

Multi-agent orchestration in herdr using @ style mentions
▲ 14 r/herdr

Multi-agent orchestration in herdr using @ style mentions

Been building something for herdr that seems useful. I built a plugin(and agent skill) that lets agents and shell panes collaborate with each other with @ mentions.

You can define “personas” and let your team of agents figure out how to work together.

Give it a shot at let me know if it’s useful

github.com
u/MediocreOchre — 4 days ago
▲ 15 r/herdr

Pi Herdsman update: Coordinating multiple Pi agents across Herdr workspaces and Git worktrees (live demo)

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?

u/j3free — 5 days ago
▲ 8 r/herdr

what does your workflow look like

do you think herdr is decent on managing multi agent workflows? for example are you easily aware which agent belongs to which project and its worktree status? are you easily capable of working on 4-5 different projects on herdr? please let me know and how

reddit.com
u/imbikingimbiking — 13 days ago
▲ 15 r/herdr

bigtty - Native macOS client for Herdr

I have been a cmux user for long and really liked all the features it provided and the native feel it gave.

I switched to Herdr recently because the server model just makes sense. Specially when you have multiple machines controlled by Herdr.

While the tool is very powerful, it always felt clunky to not have a native and Mac experience and all the goodness which cmux provided.

I built bigtty to fix that. If you have used cmux, you will feel right at home.

The UI/UX does diverge from a pure Herdr client, but the I believe it is worth it.

Features include:
- cmux-style sidebar for windows(spaces) and tabs, drag and drop panes
- intuitive mac keyboard shortcuts without vim-like prefix mode
- browser pane that tunnels over SSH, meaning a browser pointing to `localhost:3000` talks to the dev server running in the remote server, not your machine
- native file and diff viewer on cmd + click

It is yet another GUI client that everyone is building, but it works for me. Do check it out and let me know what you think of it.

https://github.com/v1k45/bigtty

PS: it is pronounced as big-tee.

u/v1k45 — 14 days ago
▲ 12 r/herdr

herdr-blink - yes, yet another fuzzy session picker

I know. Every terminal multiplexer gets about 14 of these, and herdr is no exception. I really did look around first. I tried a few options (herdr-navigator, herdr-bar, etc.) and none of them were quite what I wanted:

  • The built-in goto picker has quick status filters (blocked / done / working / idle) that I liked a lot. One key and you see only the agents waiting on you. Its search wasn't good enough for me, though.
  • The others had better search but not those filters.

I wanted both: the goto filters, plus real fuzzy search over agent name, pane/tab title, and workspace. So I did the reasonable thing and spent more time building a picker than I'll ever save by using it.

herdr-blink: a fuzzy agent switcher that replaces goto.

  • Agents that need me come first: blocked, then done, then working, then idle. Within each group, the most recently used is at the top.
  • The quick filters are kept: b / d / w / i.
  • fzf-style search across everything: harness, status, title, tab, workspace, repo, branch, and cwd. Space-separated terms can each match a different field, so claude api blocked does what you'd expect. 'exact, ^prefix, and !exclude work too.
  • Vim Motions: hjkl + duplication for ↓↑ and ][
  • Three views: a flat agent list, a workspaces → tabs → panes tree, and a git repos → worktrees → panes tree. The default view is configurable.
  • Harness logos in Kitty-graphics terminals. Yes, this is important.
  • It opens fast. It's one socket call, with no git subprocesses.

Install:

herdr plugin install dartyuhov/herdr-blink

Then bind dartyuhov.blink.open to a key; the README has the snippet. Feedback and bug reports are welcome.

PS: The video was made with explainroo.

PPS: Unfortunately, it doesn't work with remote (SSH) sessions yet (see this).

u/darst94 — 12 days ago
▲ 3 r/herdr

Herdr on Windows: Pasting multiline text into Claude without sending the prompt?

Hello! Anyone using Herdr on Windows wit Claude Code?

Maybe I just need to read the manuals again, but no matter if I use Ctrl+V, Ctrl+Shift+V or shift+rightclick, or any kind of combo with Ctrl+B and these, when the text enters the terminal, multiline text is split, or paste causes multiple prompts to be sent immediately.

I want to paste large blocks of multiline texts, and keep editing my prompt before sending. Any idea how to solve this without switching to Linux?

reddit.com
u/PC-Bjorn — 13 days ago
▲ 2 r/herdr

Running multiple client projects in herdr: best practice for hard isolation between sessions?

I'm running several client projects on a Mac mini, and I manage my agent sessions with herdr. Locally I have a projects/ folder containing one subfolder per client: GitHub repos, Shopify themes, Next.js apps, etc.

What I want is simple: every workspace (with its sub-sessions) must be completely isolated from the others.

A generic command, a prompt pasted in the wrong pane, or an instruction that was meant for one client must never be able to affect another client's files or sessions. I don't want to make a mistake that creates problems for a client just because of a copy-paste error.

So far I've found two options, and both have drawbacks:

  1. One macOS user per client. This gives real isolation, but it's very clunky to manage with herdr (switching users, separate environments, credentials, etc.).
  2. Claude Code / Codex sandboxes. Good in principle, but when I create a new session directly from herdr, it doesn't start with the sandbox settings and guidelines I'd want. It's easy to end up with an unrestricted session without noticing.

Questions for people who've solved this: What's the best practice for per-project isolation in herdr?

Is there a plugin, config, or pattern in herdr to enforce security or sandboxing on every new session by default? Do you scope each workspace to its own directory (per-project config, containers, separate users), and how do you make sure new sessions inherit it? Am I missing something obvious?

Thanks!

reddit.com
u/Exact-Shift8354 — 13 days ago