fix(telegram): preserve proxy env when applying autoSelectFamily dispatcher workaround by rylena · Pull Request #26239 · openclaw/openclaw

rylena · 2026-02-25T07:24:12Z

Summary

replace the global dispatcher override in src/telegram/fetch.ts from Agent to EnvHttpProxyAgent
keep the autoSelectFamily workaround for Node 22 IPv6 fallback, but preserve HTTP_PROXY/HTTPS_PROXY behavior for outbound requests
update telegram fetch tests to assert the proxy-aware dispatcher constructor is used

Why

Issue #26207 reports a regression in v2026.2.24 where replacing the global Undici dispatcher with a bare Agent causes all outbound traffic to bypass proxy environment variables. This change keeps the original network workaround while restoring proxy support.

Testing

pnpm vitest run src/telegram/fetch.test.ts src/telegram/network-config.test.ts

Fixes #26207

Greptile Summary

Replaced Agent with EnvHttpProxyAgent in the global Undici dispatcher workaround to restore HTTP/HTTPS proxy environment variable support for Telegram outbound requests. The previous implementation using bare Agent bypassed proxy settings, breaking environments that rely on HTTP_PROXY/HTTPS_PROXY variables. This fix preserves the original Node 22 IPv6 fallback workaround (autoSelectFamily) while restoring proxy functionality.

The change is minimal and surgical:

Updated src/telegram/fetch.ts to import and instantiate EnvHttpProxyAgent instead of Agent
Updated src/telegram/fetch.test.ts to mock and assert the correct constructor is used
All existing tests pass, confirming the workaround behavior is preserved

Confidence Score: 5/5

Safe to merge - targeted fix that correctly restores proxy support without affecting existing functionality
The change is minimal (single class swap from Agent to EnvHttpProxyAgent), directly addresses the reported regression in [Bug]: 2026.2.24 regression — setGlobalDispatcher breaks HTTP proxy for all outbound requests #26207, preserves the existing autoSelectFamily workaround for Node 22 IPv6 fallback, and includes comprehensive test updates. The fix follows undici's documented pattern for proxy-aware dispatchers. All tests pass, indicating no behavioral regressions.
No files require special attention

_{Last reviewed commit: db06727}

…re connected `pickDefaultNode()` returned null when multiple connected canvas-capable nodes existed and none matched the local Mac heuristic. This caused "node required" errors for agents (especially sub-agents) calling the canvas tool without an explicit node parameter. In multi-node setups, any canvas-capable node is a valid target — the receiving node broadcasts A2UI surfaces to all other connected devices. Fall back to the first connected candidate instead of failing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…carbaj03

…carbaj03)

Default missing fill field type to 'text' in /act route to avoid spurious 'fields are required' failures from relay/tool callers. Add regression test for fill payloads with ref+value only.

@qualiobra

…aw#27584 by @qualiobra) Co-authored-by: Lucas Teixeira Campos Araujo <lucas@MacBook-Pro-de-Lucas.local>

The codex forward-compat fallback only matched openai-codex, leaving github-copilot users without gpt-5.3-codex despite the model being available on the Copilot API. Made-with: Cursor

… blocking When an entry's backoff exceeds the recovery budget, the code was using break which blocked all subsequent entries from being processed. This caused permanent queue blockage for any installation with a delivery entry at retryCount >= 2. Fix: Changed break to continue so entries whose backoff exceeds the remaining budget are skipped individually rather than blocking the entire loop. Closes openclaw#27638

@Jimmy-xuzimo

…#27710) (thanks @Jimmy-xuzimo)

openclaw-barnacle · 2026-02-28T17:20:35Z