hermes-kanban-swarm
Orchestrate, configure, and execute multi-agent workflows (Swarms) using Hermes Kanban boards and profiles.
- License 许可
- MIT
- 最近更新
- 2026-10-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- hermes-kanban-swarm
- author
- Tonthong
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "hermes", "multi-agent", "swarm", "kanban", "automation", "orchestration" ] } }
- platforms
- [ "linux", "macos" ]
- description
- Orchestrate, configure, and execute multi-agent workflows (Swarms) using Hermes Kanban boards and profiles.
02 资源文件 1
- 参考文档references/google_tasks_prefect_sync.md2.5 KB
03 SKILL.md 正文
Hermes Kanban Swarm Workflows
This skill provides the standard operating procedure for configuring, deploying, and managing multi-agent swarms using Hermes Agent's native Kanban system and named profiles.
Use this skill when:
- Setting up parallel or pipelined multi-agent systems (e.g., Researcher -> Writer -> Reviewer).
- Organizing long-running collaborative tasks that must survive restarts or require human-in-the-loop review.
- Troubleshooting stuck worker tasks, dispatcher routing, or profile configuration.
1. Setup & Profile Creation
To run a multi-agent swarm, you must first define the specialized roles as independent Hermes profiles.
Step 1: Create Profiles
Create a profile for each role. Pass --description (used by the decomposer for routing) and --clone (to copy API keys, .env, configuration, and custom skills while keeping session history isolated).
hermes profile create researcher --description "Researches topics using web search and extraction tools" --clone
hermes profile create writer --description "Drafts and synthesizes research into structured markdown reports" --clone
hermes profile create reviewer --description "Reviews written text for technical accuracy and formatting compliance" --clone
Step 2: Verify Profiles
Verify that the profiles are successfully created and mapped to command aliases:
hermes profile list
Each profile has a command alias at ~/.local/bin/<profile> (e.g., researcher chat, writer setup).
2. Instantiating a Swarm
Hermes Kanban Swarms run on a shared SQLite database (~/.hermes/kanban.db for the default board).
Creating a Swarm (CLI)
Initialize a Swarm v1 graph (Parallel Workers -> Verifier -> Synthesizer) with the hermes kanban swarm command:
hermes kanban swarm "Research and write a report on the current status of Swarm AI Agent in 2026" \
--worker researcher:"Research Swarm AI Agents status" \
--verifier reviewer \
--synthesizer writer
This creates a task graph where:
- A root card (e.g.
t_19b6c277) is markeddoneimmediately to serve as the shared blackboard. - Worker tasks (e.g.
t_6a25ac43) are assigned to their respective profiles and set toready. - The verifier task is set to
todoand blocked until the workers complete. - The synthesizer task is set to
todoand blocked until the verifier passes.
3. Worker Execution & Dispatching
By default, tasks in the ready state sit in the queue until claimed by a worker lane.
Manual Dispatch (Forced Tick)
To run or test the dispatcher immediately instead of waiting for the gateway daemon:
hermes kanban dispatch
The dispatcher will automatically claim the task, create an isolated workspace under ~/.hermes/kanban/workspaces/<task_id>, and spawn the corresponding profile process (e.g., hermes -p researcher chat -q ...).
Monitoring & Auditing
Track execution progress and trace logs:
# View active tasks and their state
hermes kanban list
# Check attempt history, run count, and elapsed time for a task
hermes kanban runs <task_id>
# Display live logs or stdout of the active worker process
hermes kanban log <task_id>
4. Key Developer Invariants & Pitfalls
Ephemeral Workspaces
By default, tasks use scratch workspaces located at ~/.hermes/kanban/workspaces/<task_id>.
- Pitfall: This directory is wiped immediately upon task completion.
- Fix: If workers write files that must persist, they must copy them to a shared host path or write them directly to a directory workspace (e.g.,
dir:/absolute/path/to/project) instead of scratch space. Alternatively, log paths can be recorded in comments or metadata.
Stalled Tasks
- Symptom: Tasks remain in the
readystate indefinitely. - Cause: The dispatcher is not running.
- Fix: Run
hermes gateway start(if configured to run gateway-dispatch) or invoke manual ticks withhermes kanban dispatch.
Shared Bot Token Conflicts
- Pitfall: If multiple profiles attempt to launch the gateway (
hermes gateway run/start) using the same Telegram or Discord bot token, the processes will block each other. - Fix: Run only one main gateway dispatcher. Let worker lanes execute as command-line agents (
hermes -p <profile> chat -q) instead of standalone gateway bots.
5. External Task Synchronization (Google Tasks & Mobile Tracking)
Hermes Kanban tasks can be automatically mirrored into Google Tasks, organized by profile/assignee for real-time mobile tracking and notifications.
- Flow Script:
zero-touch-prefect/kanban_google_tasks_sync.py - Orchestration: Runs as a Prefect 2.x Flow logging to
http://100.115.66.121:4200 - Schedule: Every 1 minute via crontab and lockfile wrapper (
~/.hermes/scripts/run_kanban_google_tasks_sync.sh). - Detailed Reference: See
references/google_tasks_prefect_sync.md.
04 同仓库更多 Skills
writing-plans
Write implementation plans: bite-sized tasks, paths, code.
subagent-driven-development
Execute plans via delegate_task subagents (2-stage review).
react-composition-2026
Teaches modern React composition patterns for 2025/2026. Use when designing component APIs, building shared UI libraries, or refactoring prop-heavy components.
react-2026
Provides a comprehensive guide to the modern React 2026 stack. Use when starting a new React project or modernizing an existing one with current frameworks, build tools, routing, state management, or AI integration.
plan
Plan mode: write markdown plan to .hermes/plans/, no exec.
hermes-s6-container-supervision
Modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image — adding new services, debugging profile gateways, understanding the Architecture B main-program pattern.