hermes - 💡(How to fix) Fix Kanban dispatcher: no config key for a worker concurrency cap (`max_spawn` only reachable via CLI) [2 comments, 3 participants]

Fix / Workaround

Summary: In v0.14.0, dispatch_once() in hermes_cli/kanban_db.py supports max_spawn as a live global concurrency cap (counts running + spawned) and a max_in_progress parameter. Neither is exposed as a kanban.* config key — max_spawn is only reachable via the --max flag of hermes kanban dispatch/watch, and the default gateway-embedded dispatcher (kanban.dispatch_in_gateway: true) spawns with no cap. max_in_progress is an unwired internal parameter.

Impact: Operators running the default embedded dispatcher cannot cap concurrent workers, risking host RAM/CPU overcommit.

Ask: Expose max_spawn (and max_in_progress) as kanban.* config keys honored by the gateway-embedded dispatcher. Optionally, a resource-aware spawn gate (skip spawning below a free-RAM / free-disk threshold).