hermes - 💡(How to fix) Fix CLI messages silently dropped during tool execution [2 pull requests]

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

  • Show an error/warning that the message couldn't be delivered

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

What happened

During an active session, I typed a message while the agent was running tool calls (git branch delete, merge cleanup). The agent never received it. When I asked "did you see my queued message?" the agent said no — the message was silently dropped.

Steps to reproduce

  1. Start an interactive hermes session
  2. Have the agent run multiple sequential tool calls (e.g., git push + branch delete + checkout)
  3. Type a message during or immediately after the tool calls
  4. The agent continues without acknowledging the message

Expected behavior

Messages should either:

  • Queue and deliver when the agent is ready for input
  • Show an error/warning that the message couldn't be delivered

Actual behavior

Message silently dropped. User has no indication it was ever typed.

Impact

This is especially frustrating when the dropped message is:

  • A course correction ("wait, don't merge yet")
  • A follow-up question that the user assumes was received
  • Time-sensitive feedback

The user may continue the conversation assuming the message was seen, only to discover minutes later that it was lost.

Environment

  • CLI (terminal) session
  • deepseek-v4-pro via deepseek provider
  • macOS
  • Hermes Agent latest

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…

FAQ

Expected behavior

Messages should either:

  • Queue and deliver when the agent is ready for input
  • Show an error/warning that the message couldn't be delivered

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 CLI messages silently dropped during tool execution [2 pull requests]