hermes - 💡(How to fix) Fix [Bug]: KANBAN_GUIDANCE system prompt doesn't enforce write_file tool use — tested many models hallucinate file writes to workspace

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…

Error Message

Additional Logs / Traceback (optional)

Root Cause

The KANBAN_GUIDANCE block in agent/prompt_builder.py (line 204-206) tells workers to "cd
$HERMES_KANBAN_WORKSPACE before any file operations" but never explicitly instructs them to use
the write_file tool to create deliverables. The TOOL_USE_ENFORCEMENT_GUIDANCE block prevents the
model from stopping early with a summary, but models pattern-match "describe the file" as a valid
output because there's no disambiguation between "write the file with the tool" and "describe
what the file would contain."

Fix Action

Fix / Workaround

I can patch the prompt builder locally. Simple change — add a step 2a that says "Use the
write_file tool at $HERMES_KANBAN_WORKSPACE to create deliverables. Do not describe what you
would write — call the tool."

Code Example

Debug report uploaded:
  Report       https://paste.rs/6h76D
  agent.log    https://paste.rs/6q2fy
  gateway.log  https://paste.rs/UCWMB

---
RAW_BUFFERClick to expand / collapse

Bug Description

The KANBAN_GUIDANCE block in agent/prompt_builder.py (line 204-206) tells workers to "cd
$HERMES_KANBAN_WORKSPACE before any file operations" but never explicitly instructs them to use
the write_file tool to create deliverables. The TOOL_USE_ENFORCEMENT_GUIDANCE block prevents the
model from stopping early with a summary, but models pattern-match "describe the file" as a valid
output because there's no disambiguation between "write the file with the tool" and "describe
what the file would contain."

 Tested models that hallucinate file writes (all produce detailed file contents in summary/comment     
 but workspace directory is empty or non-existent):                                                    
 - deepseek-v4-flash                                                                                   
 - deepseek-v4-pro                                                                                     
 - grok-4.3                                                                                            
                                                                                                       
 The only model that reliably executes write_file calls is claude-opus-4-7. This suggests the          
 instruction is too ambiguous and needs an explicit step like "Use the write_file tool to create       
 each deliverable file at $HERMES_KANBAN_WORKSPACE/<filename>. Do not describe what you would          
 write — actually write it."

Steps to Reproduce

have any task that requires a file as output to be created

Expected Behavior

when the output says it has created file in the kanban/workspace/{taskid}/{fimename}.md that the write file tool call is made and the file exists.

Actual Behavior

when the output says it has created file in the kanban/workspace/{taskid}/{fimename}.md that no write file tool call is made and the file does not exist.

Affected Component

Other

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Debug report uploaded:
  Report       https://paste.rs/6h76D
  agent.log    https://paste.rs/6q2fy
  gateway.log  https://paste.rs/UCWMB

Operating System

MacOS 26.5

Python Version

3.14.4

Hermes Version

Hermes Agent v0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

I can patch the prompt builder locally. Simple change — add a step 2a that says "Use the
write_file tool at $HERMES_KANBAN_WORKSPACE to create deliverables. Do not describe what you
would write — call the tool."

I did and it worked :)

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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

hermes - 💡(How to fix) Fix [Bug]: KANBAN_GUIDANCE system prompt doesn't enforce write_file tool use — tested many models hallucinate file writes to workspace