How-To Series · 6: Working While You Sleep

Kanban · Multi-Gateway

Run one kanban board across several per-profile gateways with a single dispatcher and profile-owned delivery.

After this videoYou can run one kanban board across many Hermes gateways without any two of them racing to start the same task.

When you run more than one Hermes gateway, one per profile, each opens its own connection to platform APIs and delivers messages for its profile's subscribers. Kanban task subscriptions also cover review feedback. The key rule is a single dispatcher: only one gateway owns kanban.dispatch_in_gateway (the default), and every other gateway sets it to false, so no two gateways race to spawn the same work. Delivery stays profile-owned, and an atomic event claim prevents duplicate delivery. Non-dispatch gateways still deliver for their own platforms.

About these resources. Every command in this video comes from the Kanban Multi-Gateway Deployment doc.

New words here · Plain English

one sentence each · full glossary
GatewayThe Hermes process that connects your agent to a chat app. One profile gets one gateway.
DispatcherThe single gateway that owns spawning tasks off a kanban board. Everything else just listens.
ProfileA separate Hermes setup with its own bot, memory, and sessions. Running several means running several gateways.

Sources · What this video distills

1 docs page · every command below traces to it
Primary guide
Kanban Multi-Gateway Deployment
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
Disable dispatch on a non-owner gatewayfrom source ↗
HERMES_KANBAN_DISPATCH_IN_GATEWAY=false

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this