NousResearch/hermes-agent

Profile-scoped status misreporting multiplexed Telegram adapter connection state

Cluster 139080. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #139272 on 15 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #139272, then check it covers your case.

Read #139272 Pick up a Lab task

These members appear to concern how status for a served, multiplexed profile is reported, including a bug report that /api/status shows Telegram as disconnected and two fix-oriented changes referencing the multiplex runtime or multiplexer record. The titles alone do not confirm the cause or whether the changes address the report.

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.

#139272 fix(gateway): report a served profile's adapters from the multiplexer record

merged to main

files: gateway/status.py, gateway/status_served.py, hermes_cli/web_routers/messaging.py, hermes_cli/web_routers/status.py, tests/hermes_cli/test_served_profile_mirror_platforms.py, tests/hermes_cli/test_web_server_gateway_topology.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#139094 fix(status): use multiplex runtime for served profile status · superseded by another PR → #139272, #134889

Closed issues · 1

Closed#139080[Bug]: profile-scoped /api/status reports a multiplexed profile's Telegram as disconnected (Desktop shows "telegram down")

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

Merged PRs: #139272
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Oct 2026

For your agent

The same facts, typed.

cluster/139080.json
cluster/139080.md