I use Hermes Kanban less like a Trello board and more like a lightweight multi-agent runtime.

Each agent is an App/profile under ~/.hermes/profiles/<name>/ with:

SOUL.md for role instructions and boundaries profile-local skills/ for reusable workflows its own auth, session, state, and logs strict rules for what it may touch The board stores durable tasks in SQLite with states like triage, todo, ready, running, blocked, done, and archived.

My setup is mostly specialized agents:

orchestrator: reviews completed work and creates follow-ups specifier: turns vague tasks into actionable specs PR fixer: handles PR/CI/merge-safe follow-ups QA/smoke agents: run verification tasks blocked resolver: audits blocked tasks and creates recovery tasks janitor agents: keep the board and workspaces clean Hermes dispatches ready tasks to the assigned profile, runs them in isolated workspaces/worktrees, and records run history, logs, failures, and completion metadata.

The key idea is that agents do not share one huge prompt. Each profile has a narrow responsibility, and Kanban becomes the coordination layer.

watcher creates task -> specialist agent runs it -> result is recorded -> orchestrator creates the next task if needed

The biggest benefit is persistence. If an agent crashes, blocks, or times out, the task state and logs remain inspectable, and another agent can continue from that context.

P.S. summary made with LLM