6 phút đọc
eliasstravik/herdr-projects: A coordinator conversation, parallel worker threads, shared memory and an overview of what – Repository eliasstravik/herdr-projects. Mô tả: A coordinator conversation, parallel worker threads, shared memory and an overview of what needs you. A Herdr plugin.. 458 stars, 20 forks, ngôn ngữ chính Rust, cập nhật 2026-09-25.
1. Repository làm gì?
Run a whole project across your coding agents without handing each one its task or keeping track of who is doing what
Herdr Projects lets you run a larger piece of work in Herdr when one agent isn't enough and managing five by hand is a job in itself. You talk to one coordinator agent. It starts a separate agent for each task on its own branch, gives every one of them the same goal, instructions and memory, and Herdr's own sidebar shows you which threads need you, which are ready for review and which are still working.
✓ Free, MIT licensed ✓ Runs on your machines, no hosted service ✓ macOS and Linux, Herdr 0.9.1+
Keep one conversation going while the work happens in parallel
The coordinator never does the work itself, so it's always free to answer you. Each task runs in its own thread: a separate agent in its own git worktree and branch, or in its own folder when there's no repository. You read reports and answer the threads that need you instead of briefing every agent yourself.
Choose between briefing each agent by hand, one long agent session, a cloud projects product, or a coordinator in Herdr
2. Dữ liệu và cấu trúc đáng chú ý
Keep your attention on decisions. Herdr Projects starts and tracks the threads, your agents do the work, and you choose what to review, answer, or merge.
Tell the coordinator what you want. See which thread needs you in the sidebar.
Each thread's sidebar row shows its id and title, and a line under it with what Herdr's own state word does not say (review · PR #4, ~40%) and the agent's own activity. Agents and spaces are grouped by project on a rail (┌─ Herdr Projects … └─) whose colour is the project's state: heavy red when something needs you, lilac when something works, grey when idle; the coordinator comes first and then its threads with what needs you first; everything else sits on a dashed other rail. The tab bar says projects: 2 need you. prefix+a opens one popup with threads, tasks, inbox, routines and settings, where every thread's own list of next steps is a number key away.
⚡ Stop briefing every agent yourself
Say what you want once. The coordinator proposes threads and waits for your go-ahead, then each thread starts from a brief with the project's goal, your standing instructions, the project's memory and its task, on the agent you pick (Claude Code, Codex, OpenCode or any other kind Herdr runs). Lessons a thread reports under ## Remember flow back into memory for the next one.
💬 Know when a thread needs an answer
Agents report their own progress, so a thread that asked you something shows needs you even when it looks idle, and you get a notification that names the project and the thread. A background ticker follows pull requests: failing checks and review comments go back to the thread to fix, and a merged pull request resolves the thread and removes its worktree and branch once its agent has finished (it may still be tagging or deploying).
3. Khả năng ứng dụng và giới hạn
Open your first project in three steps
Once, if you're on 0.2.2 or older (herdr-projects –version), which has no update yet:
Herdr reinstalls the plugin in the same folder, so your ~/.local/bin/herdr-projects link keeps working. If you linked a local checkout with herdr plugin link instead, run git pull and sh scripts/install.sh in it in place of the herdr plugin install line.
update works for both install types and changes nothing when you're already on the newest release. Its doctor –fix also links the autoproject skill for each harness you configured, so existing users don't need to run configure again. A linked checkout must be on main with no uncommitted changes, or update stops and says why. When the install fails, the old version stays installed and the ticker is restarted. doctor says when a newer version is out.
You need to be comfortable in a terminal. The plugin downloads its own prebuilt binary on install, and a project is a plain folder of Markdown and TOML files, but you never have to edit them: everything changes by asking the coordinator or from the popup. You'll need macOS or Linux, Herdr 0.9.1 or newer, Git, and an agent CLI Herdr can start, such as Claude Code. Rust/Cargo is needed only when there is no prebuilt binary for your machine. The getting-started guide covers the prerequisites.
How do I check that Herdr Projects is running?
The command checks the Herdr version, the tools it calls, the ticker, and each project's session. The getting-started guide walks through a project that won't open, a thread that doesn't start, and a ticker that isn't running.
What permissions does the coordinator need?
It runs the herdr-projects binary every turn, so you'll want to allow-list it in your agent by subcommand, never the bare binary. Allow reading and steering (skill, context, report, inbox done, thread list, thread prompt, thread next, thread read, thread keys and the like) and leave thread resolve, sweep, delete, routine approve and configure on your agent's normal permission prompt. Leave thread start off the list too unless you've set start_threads = "auto": then every thread start is a real confirmation. Operations has the exact patterns.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
