NousResearch/hermes-agent

Telegram polling state reporting inaccuracies

Cluster 101391. Data as of 2026-10-24 04:06 UTC

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

open issues

open PRs

items grouped

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

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

Read #101664 Pick up a Lab task

These issues and fixes address incorrect connectivity status being published during Telegram polling — specifically, 'connected' being reported prematurely or when polling is unconfirmed, degraded, or not actually running. Changes aim to publish more accurate states such as 'retrying' or 'degraded' in those conditions.

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.

#101664 fix(telegram): publish retrying, not connected, while polling is unconfirmed or dead (salvage #101406)

merged to main

files: gateway/platforms/base.py, gateway/run.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_platform_reconnect.py, tests/gateway/test_telegram_send_path_health.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#101406 fix(telegram): do not publish connected for a degraded, unconfirmed polling path · merged via another change → #101664
#101473 fix(telegram): publish 'degraded' when polling did not start, not 'connected' · superseded by another PR → #101406

Closed issues · 1

Closed#101391Telegram: gateway_state.json reports state=connected for hours while the adapter is not polling — 'connected' is written on connect attempt, not on sustained getUpdates

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.50: 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: #101664
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 2 Sep 2026

For your agent

The same facts, typed.

cluster/101391.json
cluster/101391.md