hermes - 💡(How to fix) Fix Kanban dispatcher accepts kanban_complete with zero tool calls (no tool-evidence gate)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Workers can call kanban_complete with zero tool calls. The dispatcher accepts completion with no protocol_violation and marks the card done. Workers fabricate prose summaries without any real tool execution.

Root Cause

Workers can call kanban_complete with zero tool calls. The dispatcher accepts completion with no protocol_violation and marks the card done. Workers fabricate prose summaries without any real tool execution.

Fix Action

Fix / Workaround

Summary

Workers can call kanban_complete with zero tool calls. The dispatcher accepts completion with no protocol_violation and marks the card done. Workers fabricate prose summaries without any real tool execution.

Repro

  1. Gateway dispatches a kanban card to a worker (hermes -p default chat -q "work kanban task <id>")
  2. Worker receives card context, emits prose describing completed work
  3. Worker calls kanban_complete with a plausible-sounding summary
  4. Dispatcher accepts, marks card done
  5. Session metadata: 1 user message, 0 tool calls

Expected

Dispatcher should require at least one non-kanban tool call before accepting kanban_complete, or emit a protocol_violation and auto-block if result is empty / tool evidence absent.

RAW_BUFFERClick to expand / collapse

Summary

Workers can call kanban_complete with zero tool calls. The dispatcher accepts completion with no protocol_violation and marks the card done. Workers fabricate prose summaries without any real tool execution.

Repro

  1. Gateway dispatches a kanban card to a worker (hermes -p default chat -q "work kanban task <id>")
  2. Worker receives card context, emits prose describing completed work
  3. Worker calls kanban_complete with a plausible-sounding summary
  4. Dispatcher accepts, marks card done
  5. Session metadata: 1 user message, 0 tool calls

Observed

Card marked done. No protocol_violation event. No enforcement.

Expected

Dispatcher should require at least one non-kanban tool call before accepting kanban_complete, or emit a protocol_violation and auto-block if result is empty / tool evidence absent.

Evidence

Cards t_15e4dedf and t_7402e524 (hermes-default profile, version as of 2026-05-26). Session metadata shows 0 tool calls. KANBAN_GUIDANCE content not rendered into worker session despite --skills kanban-worker flag in spawn command.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING