Platform: Telegram
Issue: The Telegram typing indicator ("...typing") disappears mid-conversation, making it appear Hermes has gone silent — even while actively generating a response or running tools.
Reproduction (100% reproducible on ai.home):
- Send Hermes a query that requires tool use
- Hermes begins responding with a message ending in a colon, e.g. "Checking:", "Scanning:", "Looking at:"
- The Telegram typing indicator disappears immediately after that colon
- Hermes continues working (tools fire, response generates) but the typing indicator never returns
- The final response eventually arrives — it was never actually silent
Root cause (per investigation):
- Telegram's
sendChatAction(typing) has no keepalive — it expires after ~5 seconds
- When Hermes sends the first text token, Telegram clears the typing state
- If Hermes is still generating the response, the indicator stays gone
- Exacerbated when the message ends with a colon — the colon signals "action incoming" and Telegram clears the typing state exactly at that transition point
Existing related issue: Feature request for "Support explicit gateway typing indicator modes" — continuous vs thinking.
Impact: Makes Hermes appear unresponsive during normal multi-tool operations, even though all responses are being delivered correctly.
Workarounds noted:
- Avoid ending messages with colons (workaround, not fix)
- Periodic typing pings every ~4 seconds during active tool use (not currently implemented)
Platform: Telegram
Issue: The Telegram typing indicator ("...typing") disappears mid-conversation, making it appear Hermes has gone silent — even while actively generating a response or running tools.
Reproduction (100% reproducible on ai.home):
Root cause (per investigation):
sendChatAction(typing)has no keepalive — it expires after ~5 secondsExisting related issue: Feature request for "Support explicit gateway typing indicator modes" — continuous vs thinking.
Impact: Makes Hermes appear unresponsive during normal multi-tool operations, even though all responses are being delivered correctly.
Workarounds noted: