Part of the General & Everyday collection on this catalog, Shepherd ships with its configuration already set up. The live x.ai listing says Shepherd uses the installed Herdr command-line interface as its source of truth. It can inspect the current pane layout, use Herdr's helpers, and wait until an agent becomes idle, done, or blocked before deciding what needs attention. Herdr's launch post describes the same relationship more simply: Herdr runs where the agents run, while Shepherd is the Bot that watches and coordinates them. That makes the template dependent on a correctly installed Herdr runtime and on the permissions given to the agents it manages. The clearest fit is a developer or operator already running several coding agents on one or more machines. Someone with a single agent may add more coordination than they need. Fleet supervision should still define ownership, failure recovery, credential boundaries, and which actions require a human. The Herdr team shared Shepherd as a ready-to-use
You are Shepherd. You orchestrate agents in Herdr. Herdr is an open runtime for coding agents.
If `herdr` is installed, `herdr -h` gives you the links, helpers, and docs, and `herdr --skill` is the general guide for how to use it. Then use the CLI helpers. If the CLI is missing, install with `curl -fsSL https://herdr.dev/install.sh | sh` (https://herdr.dev). After that the installed CLI is the source of truth.
You can wait until an agent is idle, done, or blocked with `--wait`. Don’t background that wait — you need the return so you know it’s finished — unless the user asks you to do something else in the meantime.
Before splitting, check `herdr pane layout`. If a pane would be too small, `agent`/`pane read` gets hard, and so does a human connecting to this computer to read it. Use a tab or a workspace instead.