Kanban (Multi-Agent Board)
Kanban (Multi-Agent Board)
Start with meaning, then move to detail.
This lesson explains Kanban (Multi-Agent Board) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Two surfaces: the model talks through tools, you talk through the CLI, Kanban vs. delegatetask, Core concepts, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Kanban (Multi-Agent Board) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Tool
- A structured action the agent can call to read or change something.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Durable SQLite-backed task board for coordinating multiple Hermes profiles
What does the source say, and in what order?
- 01Two surfaces: the model talks through tools, you talk through the CLI
Start here to understand the core idea or structure.
- 02Kanban vs. delegatetask
Read this after the foundation, then connect it to the previous step.
- 03Core concepts
Read this after the foundation, then connect it to the previous step.
- 04Boards (multi-project)
Read this after the foundation, then connect it to the previous step.
- 05Managing boards from the CLI
Read this after the foundation, then connect it to the previous step.
- 06Managing boards from the dashboard
Read this after the foundation, then connect it to the previous step.
- 07File attachments
Read this after the foundation, then connect it to the previous step.
- 08Quick start
Read this after the foundation, then connect it to the previous step.
- 09Gateway-embedded dispatcher (default)
Read this after the foundation, then connect it to the previous step.
- 10Idempotent create (for automation / webhooks)
Finish here to verify the result and special cases.
Copy only after you understand the effect.
# See what's on disk. Fresh installs show only "default".
hermes kanban boards list
# Create a new board.
hermes kanban boards create atm10-server \
--name "ATM10 Server" \
--description "Minecraft modded server ops" \
--icon 🎮 \
--switch # optional: make it the active board
# Operate on a specific board without switching.
hermes kanban --board atm10-server list
hermes kanban --board atm10-server create "Restart ATM server" --assignee ops
# Change which board is "current" for subsequent calls.
hermes kanban boards switch atm10-server
hermes kanban boards s# 1. Create the board (you)
hermes kanban init
# 2. Start the gateway (hosts the embedded dispatcher)
hermes gateway start
# 3. Create a task (you — or an orchestrator agent via kanban_create)
hermes kanban create "research AI funding landscape" --assignee researcher
# 4. Watch activity live (you)
hermes kanban watch
# 5. See the board (you)
hermes kanban list
hermes kanban stats# config.yaml
kanban:
dispatch_in_gateway: true # default
dispatch_interval_seconds: 60 # defaultRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.