Cairn
NousResearch/hermes-agent

Telegram group chat request isolation bug and fix

Cluster 33288 · gateway. Data as of

Nothing open on GitHub. No fix on record.

The short answer

0open issues
0open PRs
2items grouped
Known?
Yes. 2 related items grouped here, 2 issues already closed.
Fix event
No merged or attempted fix PR is on record for this cluster.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where the Telegram gateway mixes or queues independent requests in shared group chats, creating unsafe business workflows, along with a related fix normalizing thread IDs in group gating via a shared helper.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Closed issues · 2
  • Closed#33288[Bug]: [Bug]: Telegram gateway mixes/queues independent operational requests in shared group chats; business workflows become unsafe under active sessions and runtime failures
  • Closed#33293[Bug]: Telegram gateway mixes/queues independent operational requests in shared group chats; business workflows become unsafe under active sessions and runtime failures
How this cluster was grouped
  • Link evidence (automated judgement only): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
  • Read the members yourself before treating them as one problem.
  • Pairwise link density 0.36: 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
2
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/33288.json
cluster/33288.md