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)

---

PR #74163: WORKING: All Microsoft Issues and PRs (refresh)

• Repository: openclaw/openclaw
• Author: BradGroux
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74163

Description (problem / solution / changelog)

Microsoft Ecosystem Issues & PRs Tracker

Purpose: Living checklist for maintainers to track all open Microsoft-related issues and PRs (Teams, Windows, WSL, Azure, M365/SharePoint).

How to use:

• Mark items resolved by editing this PR body and changing [ ] to [x]
• Claim items by adding your GitHub handle to the Assignee column
• Priority guide: P0 = crash/blocker/security, P1 = significant bug/regression, P2 = minor bug/enhancement, P3 = nice-to-have/stale
• Items marked (stale) have been flagged by the stale bot due to inactivity

Last updated: 2026-04-29 (post-purge audit: refreshed from currently open GitHub issues/PRs and rebuilt from PR #49126 format)

---

Summary

---

1. MS Teams Channel Plugin — Issues

Bugs / Crashes

Feature Requests

---

2. MS Teams Channel Plugin — PRs

---

3. Windows Platform — Issues

Bugs / Crashes

Feature Requests

---

4. Windows Platform — PRs

---

5. WSL (Windows Subsystem for Linux) — Issues

Bugs / Crashes

Feature Requests

---

6. WSL (Windows Subsystem for Linux) — PRs

---

7. Azure (Provider / Infrastructure) — Issues

Bugs / Crashes

Feature Requests

---

8. Azure (Provider / Infrastructure) — PRs

---

9. Microsoft 365 / SharePoint — Issues

Bugs / Crashes

No currently open items found.

Feature Requests

No currently open items found.

---

10. Microsoft 365 / SharePoint — PRs

No currently open items found.

---

Appendix: P0 Blockers (Start Here)

Appendix: High-Priority Bugs / Regressions

Appendix: Stale Items (Consider Closing)

Audit Notes

• Rebuilt from the format of PR #49126 after the issue/PR purge.
• Source set is currently open GitHub issues and PRs from openclaw/openclaw; closed counts are intentionally reset to 0 for this refreshed tracker.
• Included title/label matches for msteams, Microsoft Teams, Windows, WSL, Azure, Entra/AAD, MSAL, managed identity, DefaultAzureCredential, Microsoft Graph, SharePoint, OneDrive, and Microsoft 365.
• Kept broad multi-channel PRs when they carry channel: msteams, because those can still affect the Microsoft surface area.
• Generated with node scripts/generate-microsoft-tracker.mjs so the tracker and PR body can be refreshed after future triage passes.

Changed files

• CHANGELOG.md (modified, +1/-0)
• MICROSOFT_TRACKER.md (added, +398/-0)
• scripts/generate-microsoft-tracker.mjs (added, +428/-0)

---

PR #6457: fix(telegram): register commands for group scope + preserve topic thread params

• Repository: openclaw/openclaw
• Author: dae-sun
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/6457

Description (problem / solution / changelog)

Problem

• Telegram forum topics can show "This command is not available" for slash commands unless bot commands are registered for group scope.
• Some auth/diagnostic command responses could be sent without message_thread_id and land in the General topic.

Fix

• Register Telegram bot commands with both default scope and all_group_chats scope via setMyCommands.
• Ensure auth/diagnostic sendMessage responses in resolveTelegramCommandAuth include correct forum topic thread params (omitting General topic id=1 as required).
• Ensure plugin-command "Command not found" message also preserves topic thread params.

Tests

• Updated src/telegram/bot-native-commands.test.ts to assert setMyCommands is called with all_group_chats scope.
• Ran: pnpm vitest run src/telegram/bot-native-commands.test.ts

<!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3>

This PR updates Telegram native command handling in two ways: (1) it registers bot commands for both the default scope and the all_group_chats scope to avoid Telegram forum-topic clients showing “This command is not available”, and (2) it preserves forum topic routing (via message_thread_id, omitting General topic id=1) for auth/diagnostic and “Command not found” replies so responses stay in the invoking topic.

The changes are localized to src/telegram/bot-native-commands.ts, with a small test update in src/telegram/bot-native-commands.test.ts to cover the added group-scope registration behavior.

<h3>Confidence Score: 4/5</h3>

• This PR is likely safe to merge, with one functional follow-up needed to keep command scopes consistent when disabling commands.
• Changes are small and targeted (adding thread params to a few sendMessage calls and registering commands in an additional Telegram scope). Main risk is behavioral inconsistency: group-scoped commands may remain registered if native commands are later disabled, since the disable path only clears the default scope.
• src/telegram/bot-native-commands.ts

<!-- greptile_other_comments_section -->

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

Context used:

• Context from dashboard - CLAUDE.md (source)
• Context from dashboard - AGENTS.md (source)

<!-- /greptile_comment -->

Changed files

• src/telegram/bot-native-commands.test.ts (modified, +49/-23)
• src/telegram/bot-native-commands.ts (modified, +58/-36)