kanban-worker

To prevent stalled tasks during multi-agent Kanban dispatch, apply structured handoff shapes and retry diagnostics. This ensures workers receive clear signals, reducing miscommunication and preventing tasks from entering endless escalation loops.

The best way to handle task blocking in a Hermes worker workflow is using the kanban_block flow with safety-conscious prompts. This documents the block condition, triggers diagnostic patterns, and maintains a defined lifecycle to prevent cross-task leakage.

To isolate workspaces in Kanban workflows, configure workspace kinds such as scratch, dir:<path>, or worktree. This tenant isolation approach prevents cross-task leakage by ensuring each Hermes worker operates within a strictly bounded environment.

Yes, Hermes multi-agent orchestration supports task handoff and retry patterns. The Kanban guidance provides exhaustive shapes for worker orchestration, covering kanban_create, kanban_complete, and kanban_show flows with built-in edge-case handling.

Use kanban_complete when a dispatched task finishes successfully, and use kanban_block when hitting unresolved edge cases or dependencies. Applying the correct flow maintains lifecycle integrity and provides diagnostic patterns for stalled worker tasks.