Cairn
NousResearch/hermes-agent

Multi-bot Telegram multiplexing routing fixes and features

Cluster 8287 · 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, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR 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 issues and pull requests address supporting multiple Telegram bots sharing a single gateway with isolated sessions, and fixing routing bugs where responses were delivered through the wrong bot or adapter due to chat ID collisions and missing profile scoping.

Open issues1

  • Issue#8287Support multiple Telegram bots connecting to the same agent (same gateway, different sessions) using the same Telegram account.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #67455 feat(gateway): multi-account Telegram — one gateway, N bots, isolated sessions (#8287) · superseded by another PR → #8287, #86497, #86532, #87556
Closed issues · 1
  • Closed#17068feat(gateway): include bot identity in session_key for multi-bot Telegram setups
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/8287.json
cluster/8287.md