Herdr Recap — Git skill for Claude Code

herdr-recap

Where every agent got to, in one [herdr](https://herdr.dev) popup: what needs you, what's done, what each one was doing, and a line to answer it from without leaving the list.


Why

One agent is a conversation. Five are a job. Each works in its own pane, on its own branch, at its own pace, and the state of each lives only in that pane's scrollback. While you're in one, the others carry on without you: one finishes, one stops to ask permission for a command, one goes down a path you'd have stopped.

Then you look away for a meeting or lunch, and come back to a sidebar that says *done*, *done*, *working*, *needs you*. It tells you **that** each agent moved, not **what** it did, what it's asking, or what's next. So you rebuild it one pane at a time: open it, scroll up past the tool output, piece together what you'd asked for and what it made of it, and move on to the next. Meanwhile the agent that needed a yes has been waiting the whole time, behind the ones that didn't.

Keeping all of that in your head is the hard part of running several agents at once. herdr-recap keeps it for you: for every agent, a one-line recap of where it got to, written while you were away, with the details that decide what to look at first.

Scan the list

Open it (`prefix+alt+r`) and read down. Each agent is a few lines:

• Status first, what needs you at the top. herdr's own glyphs and colours: ◉ needs you, ◔ working, ● done, ✓ idle. Within a status, whatever has waited longest comes first, and the right side says for how long: waiting 2m, done 12m, working 18m.
• What it's waiting for. An agent stopped on a question or an approval shows it in red: the question, or the command or edit it wants to run.
• Where it got to. Claude Code's own recap of the session: the goal, the current step, the next one. The same summary