PR #74151: fix(telegram): honor ALL_PROXY and OPENCLAW_PROXY_URL in transport

• Repository: openclaw/openclaw
• Author: SymbolStar
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74151

Description (problem / solution / changelog)

Root Cause

Telegram's undici-based transport (introduced ~v2026.4.24) creates its own EnvHttpProxyAgent dispatcher, but the env-proxy gate hasEnvHttpProxyConfigured('https') only checks HTTP_PROXY/HTTPS_PROXY — it ignores ALL_PROXY/all_proxy. Additionally, in installed-service environments (e.g. macOS launchd), the service env policy strips ambient proxy vars and only persists OPENCLAW_PROXY_URL, which Telegram's transport never consulted.

This caused proxy-dependent environments (e.g. mainland China) to get ETIMEDOUT/EHOSTUNREACH/UND_ERR_CONNECT_TIMEOUT errors after upgrading from v2026.4.22 to v2026.4.26.

Changes

extensions/telegram/src/fetch.ts

• Switch env-proxy detection from hasEnvHttpProxyConfigured('https') → hasEnvHttpProxyAgentConfigured() which also considers ALL_PROXY/all_proxy
• Pass resolveEnvHttpProxyAgentOptions() to EnvHttpProxyAgent constructor so undici receives explicit httpProxy/httpsProxy values derived from ALL_PROXY (undici's EnvHttpProxyAgent does not natively read ALL_PROXY)
• Fall back to OPENCLAW_PROXY_URL env var as an explicit proxy when no standard proxy env vars are available — covers installed-service environments

src/plugin-sdk/fetch-runtime.ts

• Export hasEnvHttpProxyAgentConfigured and resolveEnvHttpProxyAgentOptions from the plugin SDK so extensions can use the ALL_PROXY-aware helpers

Related

• Fixes #74014
• #74086 (Windows variant of same root cause) may also benefit from this fix

Changed files

• extensions/telegram/src/fetch.ts (modified, +15/-4)
• src/agents/tool-allowlist-guard.test.ts (modified, +2/-3)
• src/agents/tool-allowlist-guard.ts (modified, +6/-6)
• src/plugin-sdk/fetch-runtime.ts (modified, +2/-0)