Cairn
NousResearch/hermes-agent

Telegram DM topic state not namespaced per profile

Cluster 76423 · gateway. Data as of

Nothing open on GitHub. Fix merged in #101249 on 2 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #101249. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #101249. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where telegram_dm_topic_mode and telegram_dm_topic_bindings in the shared state.db are not scoped per profile under multiplexed configurations. The work involves namespacing or separating those entries by profile to prevent cross-profile interference.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #101249 fix(telegram): multiplexed profiles keep separate DM topic lanes in the shared state.db (#76423 #87239, salvage #76487)

    merged to main

    files: contributors/emails/[redacted:email], gateway/platforms/base.py, gateway/run.py, gateway/slash_commands.py, hermes_state.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_telegram_topic_profile_isolation_76423.py, tests/gateway/test_telegram_topic_profile_routing_76423.py, tests/test_hermes_state.py, website/docs/user-guide/messaging/telegram.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #76487 fix(gateway): namespace telegram topic mode by profile under multiplex · merged via another change → bb7838c, #101249
Closed issues · 1
  • Closed#76423Multiplex: telegram_dm_topic_mode and telegram_dm_topic_bindings lack profile dimension in shared state.db
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
Merged PRs
#101249
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/76423.json
cluster/76423.md