NousResearch/hermes-agent

Telegram reconnect and TLS blocking the event loop

Cluster 133339. Data as of 2026-10-24 20:38 UTC

Nothing open on GitHub. Fix merged in #133721 on 6 Oct 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 #133721. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #133694. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #133721 Pick up a Lab task

These issues and fixes address Telegram gateway reconnection logic where synchronous TLS initialization was stalling the event loop, and where messages held during a failed reconnect attempt were not being delivered correctly after reconnection.

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.

#133694 fix(gateway): Telegram messages held by a failed reconnect attempt are delivered after the reconnect instead of lost (#133399)

merged to main

files: gateway/platforms/helpers.py, gateway/run_adapters.py, plugins/platforms/telegram/telegram_held_inbound.py, tests/gateway/test_platform_reconnect.py
#133721 fix(telegram): reconnects no longer stall the gateway loop on TLS setup (#133339, salvage #133340)

merged to main

files: agent/ssl_verify.py, contributors/emails/[email protected], plugins/platforms/telegram/adapter.py, plugins/platforms/telegram/telegram_network.py, tests/agent/test_ssl_verify.py, tests/gateway/test_telegram_closewait_limits.py

1 PR closed without merging

From the close comments: done elsewhere 1

#133340 fix(telegram): keep TLS initialization off the gateway event loop · done elsewhere → a94c106, #133721

Closed issues · 1

Closed#133339[Bug]: Telegram reconnect blocks the event loop during synchronous TLS initialization

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: #133694, #133721
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 6 Oct 2026

For your agent

The same facts, typed.

cluster/133339.json
cluster/133339.md