Run a fleet of Claude Code sessions. From the CLI — or from Claude itself.
CLI command: herd · Website: agentherder.com
herd new auth ~/Dev/myapp # new tab, claude starts
herd new api ~/Dev/myapp
herd new infra ~/Dev/myapp
herd sessions # what's running across all tabs
herd scrollback auth # read what auth is doing without switching tabs
herd send api --file task.txt # drop a prompt into any session
herd fork auth -n auth-v2 # branch a conversation, keep the originalNo tmux. No dashboard. Your terminal tabs are the UI.
When you're running multiple Claude Code sessions in parallel, you lose track fast. Which tab is working on what? Did it finish? Is it waiting for input?
herd solves this with a simple CLI that treats terminal tabs as the unit of orchestration — open them by name, read their output, send them prompts, fork them, close them. Everything stays in sync: the tab title, the Claude session name, and the working directory.
The killer feature: Claude can run herd itself. Install the skill and your Claude Code session can spawn parallel sibling sessions, monitor their output, and coordinate across them — without you switching tabs.
As a Claude Code plugin (installs the CLI + skill in one step):
/plugin marketplace add generativereality/plugins
/plugin install agentherder@generativerealityVia npm (CLI only):
npm install -g @generativereality/herdSkill only (if you already have the CLI):
mkdir -p .claude/skills/herd
curl -fsSL https://raw.githubusercontent.com/generativereality/agentherder/main/skills/herd/SKILL.md \
-o .claude/skills/herd/SKILL.mdRequirements: Wave Terminal · macOS · Node.js 20+
One-time: Wave needs Accessibility permission — System Settings → Privacy & Security → Accessibility → Wave ✓
herd sessions what's running (active/idle status)
herd list all workspaces, tabs, and blocks
herd new <name> [dir] [-w workspace] open tab, start claude
herd resume <name> [dir] open tab, run claude --continue
herd fork <tab> [-n new-name] fork a session into a new tab
herd close <tab> close a tab
herd rename <tab> <new-name> rename a tab
herd scrollback <tab> [lines] read terminal output (default: 50 lines)
herd send <tab> [text] send input — arg, --file, or stdin pipe
herd config show config path and values
Tab names match by prefix. Block IDs can be shortened to 8 chars.
herd sessions # check what's already running first
herd new auth ~/Dev/myapp
herd new payments ~/Dev/myapp
herd new infra ~/Dev/myappEach tab gets named, Claude's session name syncs to the tab title via --name.
# From a file (good for long context-heavy prompts)
herd send auth --file ~/prompts/task.txt
# Via stdin
echo "focus on the edge cases in the OAuth flow" | herd send auth
# Quick reply or approval
herd send auth "yes\n"
herd send auth "/clear\n"herd scrollback auth # last 50 lines
herd scrollback auth 200 # last 200 lines# Try a different approach without losing the original conversation
herd fork auth -n auth-v2Runs claude --resume <id> --fork-session — new independent session, full shared context from the original.
herd new api ~/Dev/myapp -w workThe real unlock: install the plugin (see Install) so Claude Code can herd itself.
With the skill installed, Claude can:
- Check what's running before starting duplicate work (
herd sessions) - Spawn a parallel session for an independent subtask (
herd new payments ~/Dev/myapp) - Monitor siblings without interrupting them (
herd scrollback payments) - Drop a prompt into any session (
herd send payments --file spec.txt) - Fork its own session to explore an alternative approach (
herd fork auth)
Claude becomes the orchestrator of its own fleet.
Claude Code's Remote Control lets you access a local session from any device — phone, tablet, browser — via claude.ai/code. The session still runs on your machine, with full filesystem and tool access.
Paired with Agent Herder, the pattern is:
- Start a command session with Remote Control enabled:
claude --remote-control "command" - From your phone or browser, connect to that session and assign work:
"Spawn three sessions — auth, payments, infra — and start them on these tasks..."
- The command session uses
herdto open tabs, send prompts, and check in on workers - You monitor and steer the whole fleet from your phone while the machine does the work
One remote-controlled session orchestrating a local fleet.
# ~/.config/herd/config.toml
[claude]
# Flags passed to every claude invocation
flags = ["--allow-dangerously-skip-permissions"]
[defaults]
# Default Wave workspace for new sessions
# workspace = ""| Terminal | Status |
|---|---|
| Wave Terminal | ✅ Full support |
| iTerm2 | Planned |
| Ghostty | Planned |
| Warp | Planned |
Wave is supported via its unix socket RPC. Other terminals will follow as adapters — PRs welcome.
MIT