{"repo":"NousResearch/hermes-agent","public_id":"8287","display_label":"Multi-bot Telegram multiplexing routing fixes and features","summary":"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.","subsystem":"gateway","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":0,"closed_issues":1,"merged_prs":0,"attempt_prs":1},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.4533333333333333},"fix_edges":[],"members":[{"kind":"issue","number":8287,"title":"Support multiple Telegram bots connecting to the same agent (same gateway, different sessions) using the same Telegram account.","url":null,"state":"open"},{"kind":"issue","number":17068,"title":"feat(gateway): include bot identity in session_key for multi-bot Telegram setups","url":null,"state":"closed"},{"kind":"pr","number":67455,"title":"feat(gateway): multi-account Telegram — one gateway, N bots, isolated sessions (#8287)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#8287","number":8287},{"kind":"pr","value":"#86497","number":86497},{"kind":"pr","value":"#86532","number":86532},{"kind":"pr","value":"#87556","number":87556}],"category":"superseded_by_pr","implication":"superseded"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}