Cairn

Fix Telegram status bubbles reused across turns/topics

NousResearch/hermes-agent · cluster 92210 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

A bug was identified where Telegram lifecycle status bubbles were incorrectly reused across different turns and topics. Fixes scope status message caching and editable statuses to be properly isolated per turn and topic.

Open issues1

  • Issue#92210[Bug]: Telegram lifecycle status bubbles are reused across turns and topics

Open PRs3

  • PR#92230fix(gateway): scope editable statuses to each turn
  • PR#92305fix(telegram): scope status message cache per turn and topic (Fixes #92210)
  • PR#106295fix(telegram): isolate turn-owned status message lifecycle
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.50: 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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/92210.json
cluster/92210.md