# NousResearch/hermes-agent · Fix Telegram status bubbles reused across turns/topics

## Open now

- 1 issue, 3 PRs open on GitHub.
- #92210: \[Bug\]: Telegram lifecycle status bubbles are reused across turns and topics
- PR #92230: fix(gateway): scope editable statuses to each turn
- PR #92305: fix(telegram): scope status message cache per turn and topic (Fixes #92210)
- PR #106295: fix(telegram): isolate turn-owned status message lifecycle

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.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 3 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#92230: fix(gateway): scope editable statuses to each turn**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `4d14d65851b2f9fe8a89ea40e214886f6c34a6c5`, `8ddf6d12347411fa43102662ba040f8280dd1415`, `#70859`, `#106295`
  - files: `gateway/run_turn_progress.py`, `plugins/platforms/telegram/adapter.py`, `plugins/platforms/telegram/telegram_status.py`, `tests/gateway/test_status_turn_ownership.py`
- **#92305: fix(telegram): scope status message cache per turn and topic (Fixes #92210)**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#78586`, `#92210`
  - files: `gateway/run.py`, `plugins/platforms/telegram/adapter.py`
- **#106295: fix(telegram): isolate turn-owned status message lifecycle**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#92210`, `#92230`, `#103260`, `#103253`, `#99905`, `#87480`
  - files: `gateway/run_turn.py`, `gateway/run_turn_runner.py`, `gateway/status_delivery.py`, `gateway/turn_context.py`, `plugins/platforms/telegram/adapter.py`, `tests/gateway/test_notification_ownership.py`, `tests/gateway/test_telegram_status_update.py`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`