# NousResearch/hermes-agent · Telegram proxy handling and transport configuration issues

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #8761: Feature Request: Extension hook for external transport configuration in TelegramAdapter

## Prior & competing PRs

- **#16008: fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#8761`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#16005: fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`