kanban-worker

To prevent worker errors in distributed kanban task execution, follow workspace handling guidance for scratch, dir:<path>, and worktree environments to avoid stale file assumptions and ensure reliable task handoffs.

Tenant isolation in multi-agent kanban workflows requires namespacing persistent memory writes safely under $HERMES_TENANT to prevent context leakage across different workers and tenants during execution.

To safely claim kanban cards, use only the return values captured from kanban_create when reporting created_cards, which prevents phantom or cross-worker claims that disrupt multi-agent orchestration.

Structure kanban_complete metadata for retry diagnostics by producing parseable completion summaries and sending timely heartbeats, enabling accurate interpretation of prior run outcomes during subsequent execution attempts.

Use kanban_block in distributed task handling when encountering specific execution obstacles, providing recommended block reasons to enable fast triage and accurate retry diagnostics for subsequent workflow attempts.

Yes, kanban-worker requires specific workspace handling behaviors for scratch, dir:<path>, and worktree workspaces to avoid stale or invalid file assumptions during distributed task execution.