{"repo":"NousResearch/hermes-agent","public_id":"8761","display_label":"Telegram proxy handling and transport configuration issues","summary":"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.","subsystem":"gateway","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":8761,"title":"Feature Request: Extension hook for external transport configuration in TelegramAdapter","url":null,"state":"closed"},{"kind":"pr","number":16005,"title":"fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock","url":null,"state":"closed","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":16008,"title":"fix(telegram): skip fallback IPs when proxy is detected to prevent connection deadlock","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#8761","number":8761}],"category":"uncategorized","implication":"needs_llm"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true}],"trust":{"default_tier":"verified","includes_suggested":false}}