Cairn
NousResearch/hermes-agent

Telegram proxy handling and transport configuration issues

Cluster 8761 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern how the Telegram adapter handles proxy environment variables, passes proxy URLs to the HTTP transport, and avoids connection deadlocks caused by fallback IP behavior when a proxy is detected. One item requests an extension hook for external transport configuration.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #16005 fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock · other
  • #16008 fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock · other → #8761
Closed issues · 1
  • Closed#8761Feature Request: Extension hook for external transport configuration in TelegramAdapter
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

Subsystem
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/8761.json
cluster/8761.md