herdr-dagr plugin
A herdr pane that draws an agent swarm as a live graph with attempts, review gates and evidence, so large runs stay readable.
- 151 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The plugin reads a run file and passes operator messages to the orchestrator.
- It needs no external services or keys.
Install
- Works in
Manual install
herdr plugin install aemrebarut/herdr-dagrFirst command in the install block. The agent skill installs separately: `npx skills add aemrebarut/herdr-dagr --skill dagr-producer -g`.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The plugin reads a run file and passes operator messages to the orchestrator.
- It needs no external services or keys.
This is third-party code. Review the repository files before installing.
What it does
herdr-dagr is a Rust plugin for the herdr terminal manager that shows agent work as an acyclic graph. An orchestrator or any agent maintains a `run.json` file in the format from `CONTRACT.md`, and the pane watches the file and draws it live. Clicking a row shows who ran the task, how long it took and whether anyone verified the result. Every attempt gets its own row with a recorded retry cause. A completion carries an evidence tier: verified, reported, heuristic or asserted. Future work is drawn dotted and only when the data producer declares it. From the pane you can send the orchestrator a message with explicit authority. The tool never writes run state itself and does not become a second workflow engine.
Who it is for. People who run five or more agents or steps in one run and want to see who did what, what was retried and what was actually verified.
Good fit when
- A swarm of agents took many steps and the thread of work was lost.
- You need to tell "the agent said done" from a verified result.
- An operator wants to send the orchestrator a hint straight from the pane.
- A plan with review loops and parallel lanes should be shown visually.
Not a fit when
- herdr is not in use and work runs in a single agent.
- You need a scheduler that starts and drives the work itself.
- You need stable Windows support, which is only a preview.
Example request
Rewrite the run plan into the dagr format: separate lanes for implementation and review, a gate before merging, and update `run.json` as work proceeds.Limitations
The pane only reads a file and plans nothing: without an agent that maintains `run.json` it stays empty. That needs the `dagr-producer` skill, and an agent without a skill system gets its text by hand through `dagr --skill`. The plugin targets herdr, with a preview `open-dagr-windows` action for Windows. Prebuilt binaries exist for released tags, otherwise the plugin builds from Rust sources. `CONTRACT.md` fixes the file format and it may change between versions.
How to disable. Remove the plugin with herdr tooling and the `dagr-producer` skill from the agent skills folder. The `run.json` files and message journal stay in the project.
FAQ
How do I install it?
Run `herdr plugin install aemrebarut/herdr-dagr` and then `npx skills add aemrebarut/herdr-dagr --skill dagr-producer -g`. The first installs the pane, the second teaches the agent to maintain the run file.
How do I open the pane?
Run `herdr plugin action invoke open-dagr --plugin herdr-dagr`. Per-side actions `open-dagr-right`, `-down`, `-up` and `-left` can be bound to keys.
What are evidence tiers?
Verified, reported, heuristic and asserted. They keep an agent saying "done" apart from a result that was actually checked.
Does the pane write run state?
No. Whoever produces the data owns it. Operator messages are saved beside it in `messages.jsonl` and sent on to the orchestrator.
Is the file validated?
Yes, the `dagr check` and `dagr stats` commands lint the format and compute flow figures.
Discussion
No questions or reviews yet.
Related
PluginsA Herdr plugin that gives every coding agent its own Telegram topic, with status in the icon and messages both ways.
A skill that builds a hierarchy of agents: a chief, per-project managers and workers in separate git worktrees inside herdr
Pi extension for background subagents: parallel delegation, a Manager, Lead and Agent chain and supervision in herdr
A package for the Pi agent: async subagents run in parallel in Herdr panes and results return on their own.
CLI that picks the agent, model and effort for a task by remaining subscription quota and launches it in a Herdr pane.
hermitd runs an always-on Claude Code agent on your machine: tasks from chat, scheduled checks and saved state after a restart.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| herdr-dagr (this card) | no | 151 | |
| Claude Squad | no | 8,790 | starts parallel sessions of different agents in tmux; herdr-dagr starts nothing and shows another run progress as a graph |
| Orchestrator | no | 119 | one agent launches others in the background; herdr-dagr draws such a run and marks what was verified |
README in short
The run file describes the plan as a graph with attempts, gates and evidence. The pane only reads it and shows it with a history that is never rewritten after the fact.