Cairn
NousResearch/hermes-agent

Telegram voice message handling and ordering fixes

Cluster 31328 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These items address bugs and fixes in how Telegram voice messages are queued, processed, and filtered—specifically around dropped responses during batching, follow-up interruption, and transcription order relative to mention filtering.

Open issues1

  • Issue#31328Telegram voice batching can drop the in-flight response when subsequent voices arrive mid-processing

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #31340 fix(telegram): transcribe voice notes before mention filter so wake-word groups can hear them · superseded by another PR → #31328
  • #31342 fix(telegram): queue voice follow-ups instead of interrupting in-flight reply (#31328) · duplicate → #8434, #19825, #31328
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/31328.json
cluster/31328.md