/crew <ask> asks what is missing, up to five questions in one batch, writes the contract and hands the card to the coordinator. From there the coordinator owns it: every stop gets one decision. A fix, a smaller scope, a split, or one concrete question back to you. Done is a proof command that exited 0, run by a tool.
›/crew add Stripe checkout for the Pro plan, in test mode
Built in, not promised: one ask fans out into up to six cards that run side by side, a card cannot be marked done until its proof passes, every run stops at its token budget, and the whole crew runs inside your own Hermes, on your own machine.
One ask. Four deliverables. All verified. Built in parallel, each one proven before it is called done.
Each station is a role with its own profile, model and tools. The two that decide whether work is done run no model at all. Why a kanban for AI agents needs a proof →
Type it in the chat you already use. Say how you would know it is done.
Reads the ask as a skeptic, asks once for what is missing, opens the card. Then the turn ends.
Wakes on every card event with the whole record in hand. One bounded turn, one decision.
One writer per card, inside the contract's scope. Stops itself after five failed tool calls in a row.
The proof command runs in a tool, exactly as it was written when the card opened. 0 is the only pass.
The coordinator re-runs the proof before the card can close. A card that asks for it gets one cheap independent verifier run instead.
One line in the thread you asked from. Or one question, after the coordinator has tried twice.
The panel reads like a transcript, not a log dump. What the worker is doing right now, what it said, which calls it made and the model it runs on. When a run stops, the same panel says why, and the coordinator’s fix sits on the card.
Crew is now a native page in Hermes Desktop’s sidebar, built from the same app as the browser dashboard and drawn in the app’s own colours. It needs no separate server and no systemd. What the board guarantees, section by section →
Open in Crewbutton that opens that card’s page.
Setup is four short steps: Crew in Hermes Desktop, in the README.
/crew runs in your chat and opens the card with the board's own tool, so the ending comes back to the thread that asked - no polling, no watcher. A card needs a full contract, and a script that writes board state or consent is refused before it exists.
The mechanical cases never reach a model: a held workspace, a dead model pin, a proof that now passes. Everything else gets one bounded turn: two retries, then one question to you. The decision turn runs -t file: it decides, does not do, and treats worker text as untrusted data.
A crew card closes only on a PASS line written by the tool that ran the proof command as it was snapshotted when the card opened. That holds for the writer, for the verifier, and for your own chat. Two FAILs go back to the coordinator with both outputs.
Verify: proof is the tool plus the audit. Verify: independent adds one cheap verifier run with one check the command cannot make. A proof command Hermes would flag waits for your own /crew-proof <card> yes — a run cannot approve its own proof.Every API call re-reads the whole context, so cost is calls times context, and Crew keeps both short. A run stops itself after five failed tool calls in a row. Every card carries a token budget, and a run that reaches it stops instead of burning on.
approvals.mode or write a crew profile’s config - that switch is yours, set once with /crew-safety.Four commands cover the daily loop, and the cheatsheet below lists all eight. Unblocking, retrying and verifying are the coordinator's job, and the board shows what it decided: each card carries its verdict, its budget and its last decision.
/crew <ask>start a card
/crew-statuswhat is running
/crew-stop <id>stop a card
/crew-diagnoseread-only look at a card
127.0.0.1:8799. No external service, no telemetry leaving the box.Install once per profile; running it twice changes nothing. Then type the ask in the chat you already use. The card, and its ending, come back to that thread.
›Set up Hermes.Crew for my Hermes profile NAME: run hermes plugins install macd2/Crew, then python3 ~/.hermes/plugins/crew/install.py --profile NAME and hermes -p NAME plugins doctor crew, and fix anything they report. Finish by sending /crew-status in my chat and tell me what it answered.$hermes plugins install macd2/Crew$python3 ~/.hermes/plugins/crew/install.py --profile NAME$hermes -p NAME plugins doctor crewStar on GitHubFree and open source · Apache-2.0
/crew and /crew-diagnose are skills that run in your own session; the other six are plugin commands. Stop, unstick, safety and proof are there so the coordinator never has to ask you to type something you did not want to type.
Crew needs Hermes Agent 0.21.5 or newer with the kanban board, and Python 3.11+. The plugin declares requires_hermes: ">=0.21.5", so an older Hermes refuses to load it.
--nightly-proofs are skipped.Terminal and Desktop read the same kanban board and session store, so a card looks the same in either, and you can use both at once. Windows details: WINDOWS.md.
The plugin is free and open source, Apache-2.0. If you use Hermes.Crew in an enterprise and would benefit from commercial support, extra tooling, or managed model spending, write to crew@forgecoreai.com and tell us what a card has to prove in your setup.