rarce

Herdr Crew — Development skill for Claude Code

Development community

herdr plugin: bring up a team of Claude Code sessions, one tab per role, plus a live status board, from a versioned .herdr/crew.toml.

How to install Herdr Crew

This entry records only its repository, not the path inside it, so there is no exact command to give. Open rarce/herdr-crew and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Herdr Crew does

herdr plugin: bring up a team of Claude Code sessions, one tab per role, plus a live status board, from a versioned .herdr/crew.toml.

Alternatives in Development

  • Herdrm — Native macOS console for herdr — all your coding agents and their live terminals, across devices 635 ★
  • Arstart — AgentRecall session opener — status board (no args), project loader ( ), or cold-start bootstrap 370 ★
  • Albert — Autonomous multi-agent harness for Claude Code (A.L.B.E.R.T. orchestrator) plus a zero-dependency live HUD con 100 ★

README

herdr-crew

**Bring up a team of Claude Code, Codex and pi sessions, one per role, from a file you keep in the repository.**

herdr-crew is a [herdr](https://herdr.dev/) plugin. You describe the project's roles once in `.herdr/crew.toml`: their prompts, whether each works in its own git worktree, and which one coordinates. After that, `cd repo && herdr` opens the project's workspace with a tab per role running its selected coding agent, plus a tab with a live status board.

![The status board of an example project, tinylink: one box per role with what it is doing now and next, what the sessions are waiting on from you, and recent events](docs/images/board.png)

  • One command, idempotent. up creates the workspace, the role tabs and their worktrees, and starts each agent with its prompt. Run it again and it only fills in what is missing; it never starts a second agent for a live role.
  • Starts with herdr. With the plugin installed, herdr's startup hook brings the project up in the workspace herdr opens. After a herdr restart it repairs only the board and leaves the resumed sessions alone.
  • More hands on demand. add and close add or remove extra instances of a role (dev-2, dev-3…), each in its own worktree if the role asks for one.
  • A status board. board draws .herdr/status.json, which the coordinating role keeps up to date, and validates it with the same rules as the JSON Schema it generates from crew.toml.
  • Checked configuration. Unknown keys and placeholders are errors reported with line and column, all at once.

See [the end-to-end demo](docs/demo.md) for one task going from assignment to review, integration and recovery, and [how sessions collaborate](docs/workflows.md#how-sessions-collaborate) for what herdr-crew does and does not coordinate. The design, with its decisions and the herdr behaviour they rely on, is in [docs/design.md](docs/design.md).

Requirements

  • herdr 0.9.1 or later, on macOS or Linux
  • Rust (stable