feat(gateway): add busy_ack_enabled config option to suppress ack messages#17491
Closed
JezzaHehn wants to merge 1 commit into
Closed
feat(gateway): add busy_ack_enabled config option to suppress ack messages#17491JezzaHehn wants to merge 1 commit into
JezzaHehn wants to merge 1 commit into
Conversation
…sages When a user sends a message while the gateway is busy processing, an acknowledgment message is sent. This can be spammy for users who send rapid messages. Add display.busy_ack_enabled config option (default: true) to allow users to suppress these busy-input acknowledgment messages. Fixes NousResearch#17457
alt-glitch
added
type/feature
teknium1
added a commit
that referenced
this pull request
May 1, 2026
- Move the disabled-ack guard above the debounce so we don't stamp _busy_ack_ts[session_key] when no ack was actually sent. Harmless (never read when disabled) but cosmetically off. - Document display.busy_ack_enabled in user-guide/messaging/index.md and HERMES_GATEWAY_BUSY_ACK_ENABLED in reference/environment-variables.md. - Add JezzaHehn to scripts/release.py AUTHOR_MAP for contributor credit. Follow-up to #17491 (Jezza Hehn).
Contributor
|
Merged via PR #18194 — your commit was cherry-picked onto current main with your authorship preserved (commit 2b512cb on main). I added a small timestamp-placement tweak (moved the disabled-ack guard above the debounce stamp so we don't record a 'last ack sent' timestamp that was never actually sent) plus docs for display.busy_ack_enabled / HERMES_GATEWAY_BUSY_ACK_ENABLED. Thanks for the clean fix! |
nickdlkk
pushed a commit
to nickdlkk/hermes-agent
that referenced
this pull request
May 11, 2026
- Move the disabled-ack guard above the debounce so we don't stamp _busy_ack_ts[session_key] when no ack was actually sent. Harmless (never read when disabled) but cosmetically off. - Document display.busy_ack_enabled in user-guide/messaging/index.md and HERMES_GATEWAY_BUSY_ACK_ENABLED in reference/environment-variables.md. - Add JezzaHehn to scripts/release.py AUTHOR_MAP for contributor credit. Follow-up to NousResearch#17491 (Jezza Hehn).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Config
How to test
Related