Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix feat(gateway): add config option to suppress busy-input acknowledgment messages [1 pull requests, 1 participants]

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…
GitHub stats
NousResearch/hermes-agent#17457•Fetched 2026-04-30 06:47:32
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
vingeraycnvingeraycn
Participants
vingeraycnvingeraycn
Timeline (top)
labeled ×4cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #17491: feat(gateway): add busy_ack_enabled config option to suppress ack messages

Description (problem / solution / changelog)

Summary

When a user sends a message while the gateway is busy processing, an acknowledgment message is sent (e.g., "⚡ Interrupting current task..."). This can be spammy for users who send rapid messages like voice input.

Add config option (default: for backward compatibility) to allow users to suppress these busy-input acknowledgment messages.

Changes

  • Add config loading for in
  • Add guard in to skip sending ack when disabled
  • Log at DEBUG level when ack is suppressed

Config

How to test

  1. Run a long terminal command (e.g., )
  2. Send a message while it's running
  3. Verify you get the ack message (default behavior)
  4. Add to config.yaml
  5. Restart gateway
  6. Repeat test - verify NO ack message is sent

Related

  • Fixes #17457

Changed files

  • gateway/run.py (modified, +8/-0)

Code Example

display:
  busy_input_mode: steer
  busy_ack_enabled: false   # new option
RAW_BUFFERClick to expand / collapse

Problem

When a user sends a message while the gateway agent is busy processing a previous turn, the gateway automatically replies with an acknowledgment message:

  • Interrupt mode: ⚡ Interrupting current task. Ill respond to your message shortly.
  • Queue mode: ⏳ Queued for the next turn. Ill respond once the current task finishes.
  • Steer mode: ⏩ Steered into current run. Your message arrives after the next tool call.

These messages are sent as a reply to every user message that arrives while the agent is busy (debounced at 30s per session). For users who send multiple consecutive messages (e.g., voice input, rapid-fire thoughts), this floods the chat with gateway notifications that add no real value — the user already knows the agent is working.

Proposed Solution

Add a display.busy_ack_enabled config option (default: true for backward compatibility) that allows users to suppress these busy-input acknowledgment messages entirely.

When set to false, the gateway should skip sending the acknowledgment text and instead just log it at DEBUG level internally.

Config

display:
  busy_input_mode: steer
  busy_ack_enabled: false   # new option

Implementation sketch

In gateway/run.py, the _handle_busy_input() method builds the ack message and sends it via adapter._send_with_retry(). A simple guard around the send block (checking the new config flag) would suffice, with a DEBUG log replacing the sent message.

Why not just remove it entirely?

Some users may find the ack helpful (especially on first encounter or when using interrupt mode), so making it opt-out preserves the experience for those who want it while letting power users silence the noise.

Related

  • Issue #7161 — Default gateway tool_progress to off (same vibes: messaging platforms should be quiet by default)
  • PR #6935 — /background command bypass (another busy-session UX improvement)

extent analysis

TL;DR

To prevent flooding the chat with gateway notifications, add a display.busy_ack_enabled config option and set it to false to suppress busy-input acknowledgment messages.

Guidance

  • Add the display.busy_ack_enabled config option to your configuration file (e.g., config.yaml) and set it to false to disable busy-input acknowledgment messages.
  • Update the _handle_busy_input() method in gateway/run.py to check the busy_ack_enabled config flag before sending the acknowledgment message.
  • If busy_ack_enabled is false, log the acknowledgment message at DEBUG level instead of sending it.
  • Verify that the fix works by testing the scenario where a user sends multiple consecutive messages while the agent is busy.

Example

if display.busy_ack_enabled:
    adapter._send_with_retry(ack_message)
else:
    logger.debug(ack_message)

Notes

This solution assumes that the display.busy_ack_enabled config option is properly propagated to the _handle_busy_input() method. Additionally, this fix may not be suitable for all users, as some may find the acknowledgment messages helpful.

Recommendation

Apply the workaround by adding the display.busy_ack_enabled config option and setting it to false, as this allows users to opt-out of the busy-input acknowledgment messages while preserving the experience for those who want it.

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…
#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING