hermes - 💡(How to fix) Fix [Bug] Gateway approval wait is not resolved by normal user replies during pending approval [1 pull requests]

When Hermes Gateway is waiting for a dangerous-command approval, only explicit /approve or /deny resolves the pending approval event. If the user replies with a normal instruction instead, for example: continue

yes, but do it another way wait, first check the status don’t restart the service, inspect it first

that message is handled as regular busy-session input rather than as an approval decision. With the default busy input behavior (display.busy_input_mode: interrupt), the normal reply may interrupt or queue the current agent turn, but it does not unblock the approval wait in tools/approval.py. The original dangerous command continues waiting until approvals.gateway_timeout expires, then returns: BLOCKED: Command timed out. Do NOT retry this command.

From the user’s perspective, this is confusing because they did respond promptly, but Hermes still reports an approval timeout.

Expected behavior When a pending approval exists and the user sends a normal text message instead of /approve or /deny, Gateway should make the state explicit, for example: A dangerous command is waiting for approval. Please reply with /approve or /deny first. Your message was queued and was not treated as an approval. Optionally, Gateway could support a clearer flow such as:

/approve /deny /deny and use this new instruction

or buttons: Approve, Deny, Deny and use new instruction

Why this matters This avoids the confusing situation where: Hermes asks for dangerous-command approval. User responds quickly with a normal instruction. Gateway treats that as busy input. The approval wait remains unresolved. Hermes eventually returns BLOCKED: Command timed out.