Guide
Ask your agent.

Everything Herdr can do is written down for your agent, inside the app, and always matches the version you have. It's all open source too, so your agent can read the code when it needs more.

##Get going

  1. Install Herdr. One line, on the download page.
  2. Start an agent from the + in the tab bar: Claude Code, Codex, or any program.
  3. Point it at the guide. That's the whole tutorial.
❯ Read ~/.config/herdr-app/AGENTS.md

Then ask for what you want. If it can be done, your agent knows how, and if it can't, it tells you why.

##Things to ask

Prompts that work. Use them as they are or as a start.

A board of your agents

❯

Make me a layout where my agents are cards in columns: needs you, working, done.

A new layout next to yours. Switch between them with ctrl-shift-l.

A timer on every tab

❯

Put a timer on each tab: how long its agent has been working.

Your agent clones the tab bar and edits the copy. Herdr's own stays untouched.

Your server in the sidebar

❯

Add my server box as a machine, then open a space there and start Claude in it.

Its agents join the same list as this computer's.

A reviewer that reports back

❯

Start a reviewer on this branch and tell me what it finds.

A helper agent under yours. It works, reports back, and your agent sums it up.

One worktree per issue

❯

Open a worktree for issue 42 and start Codex on it with the issue as its task.

A new space for the branch, nested under its repo, with the agent already on it.

Your look

❯

Use a light theme, Geist Mono at 15, and a softer sound when an agent needs me.

Your settings change for every layout that leaves them open.

A ping on your phone

❯

When an agent needs me, send a notification to my phone with ntfy.

A small mod that watches the agents and calls ntfy.sh.

Someone else's layout

❯

Read ~/.config/herdr-app/AGENTS.md, then add this layout: herdr.dev/layouts/herdrdev/pasture

Your agent reads every file first, adds it next to yours and switches to it.

##Go deeper