cd /news/developer-tools/herdr-notes · home topics developer-tools article
[ARTICLE · art-124457] src=gist.github.com ↗ pub= topic=developer-tools verified=true sentiment=· neutral

herdr notes

Herdr, a terminal multiplexer for AI agents, enables a lead agent to coordinate multiple coding agents across panes via a CLI. The tool requires installing integrations for agents like Claude, Codex, Grok, and Kimi, and uses a skill to teach the lead the CLI, preventing it from inventing MCP or ignoring other panes. The workflow includes starting agents with skip-permissions flags, listing agents, and prompting them with specific commands, with Git operations handled by the lead.

by read2 min views1 publishedSep 8, 2026

The whole product is three steps:

  1. Open Herdr in the repo.
  2. Open the agents you want in other panes.
  3. Tell the lead to talk to them with the Herdr CLI.

The skill is the how-to. The prompt is the job.

One integration per agent:

herdr integration install claude
herdr integration install codex
herdr integration install grok
herdr integration install kimi
herdr integration install antigravity-cli   # agy

Teach the lead the CLI:

npx skills add herdrdev/herdr --skill herdr -g

Without the skill, the lead often invents MCP or ignores the other panes.

cd <repo>
herdr

Open a window for each agent:

  • New tab: click + , or prefix thenc
  • Split: right-click the pane frame, or prefix then v

Start each helper in its own pane, optionally with that CLI's skip-permissions flag:

Agent Flag
claude, agy --dangerously-skip-permissions
codex, grok, kimi --yolo

Then:

herdr agent list

Use those names exactly. Do not open every agent for every task. Two helpers plus a lead is enough.

The lead must be running inside Herdr (HERDR_ENV=1). Copy names from the list. Do not put the lead on the call list.

Paste into the lead. Swap roles and the task. Need gh logged in (gh auth status) for the PR step.

You are the lead. Use the herdr CLI to talk to the other agents
in this session. Run `herdr agent list` if you need names.
Do not invent MCP, subagents, or tmux.

grok — <role>
codex — <role>
Only <writer> edits files.

Task: <one sentence>

Git:
- New branch off main. Commit when the work is done.
- Open a PR. Do not merge. Do not push to main.

Stop when the PR URL exists. Paste it.

Use this when the lead does the work itself, cannot see the other panes, or sits on agent_blocked.

Stop. You are inside Herdr. Use only the herdr CLI.

1. herdr agent list
2. Talk only to those names:
   herdr agent prompt <name> "<job>" --wait --timeout 300000
   herdr agent read <name> --source recent-unwrapped --lines 200
3. If the command returns agent_blocked: do not retry.
   Tell me the pane and wait.
4. If HERDR_ENV is not 1, say so and stop.

Git still: branch, commit, PR. No merge.
Then continue the task.
What you want What to do
Leave, keep agents running Ctrl+Space , thend (Omarchy). Stock Herdr: prefix thenq . Closing the window is the same.
Kill the session herdr server stop
prefix+x closes a pane.prefix+k closes a tab. Neither stops the server.
Reattach later herdr orSuper+Ctrl+Return
── more in #developer-tools 4 stories · sorted by recency
── more on @herdr 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/herdr-notes] indexed:0 read:2min 2026-09-08 ·