Hey Brad — Jason here. I just reached out on X as well.

I'm running an OpenClaw instance with heavy multi-channel Slack usage and hitting the cross-channel message routing bug documented in several issues this PR appears to cover:

• [Bug]: Cross-channel reply context leak — Teams DM overwrites session reply target, causing heartbeat responses to route to wrong user #24148 (Cross-channel reply context leak — Teams DM overwrites session reply target)
• [Bug] Multi-channel session routing - replies go to wrong channel #45514 (Multi-channel session routing — replies go to wrong channel)
• [Bug]: Feishu DM (p2p) messages routed to webchat instead of feishu channel #44866 (Feishu DM messages routed to webchat instead of feishu channel)

In our case, messages sent via the message tool with an explicit target channel ID intermittently route to the active session's delivery context instead of the specified target. We've been seeing this for ~30 days on Slack, affecting multiple users. Happy to provide reproduction details or test builds if that's helpful.

Appreciate the work on this — it's a significant pain point for anyone running multi-channel setups.

Update: 2026-03-26 -- Items resolved tonight

Merged PRs:

• msteams: fetch thread history via Graph API for channel replies #51643 (thread history via Graph API) -- resolves feature requests msteams: Fetch thread/chat history from Graph API on session restart #54626, feat(msteams): fetch thread history via Graph API for channel replies #43326, and issue feat(msteams): Add Graph API-based message history query (readMessages action) #11346
• msteams: add search message action #54832 (search + 7 Graph message actions) -- resolves feature requests feat(msteams): Implement read and search message actions for Teams channel #40865 and feat(msteams): Add Graph API-based message history query (readMessages action) #11346
• feat: Add Microsoft Foundry provider with Entra ID authentication #51973 (Microsoft Foundry provider with Entra ID auth) -- resolves Azure feature requests [Feature]: Support Claude Models via Azure service #7249, feat: add Azure Claude (AI Foundry) onboarding path #47181, and related issues [Feature]: Feature Request: Add Azure AI Foundry #5303, [Feature Request] Add native Azure OpenAI / Azure AI Foundry as model provider #6056, [Feature]: I tried to use foundery api it's not supported #19955 (all closed)

Superseded PRs now checked off:

• feat(msteams): add Teams reaction support #37853 (Teams reaction support) -- superseded by msteams: add reaction support with delegated auth and pagination helper #51646 (pending merge)
• feat(msteams): fetch thread history via Graph API for channel replies #43326 (thread history PR) -- superseded by msteams: fetch thread history via Graph API for channel replies #51643 (merged)

10 items marked resolved in the tracker body above.

Tracker Update: Batch Closure (2026-03-26)

Marked the following as resolved after tonight's review, comment, and closure session.

Issues Closed (resolved by merged PRs)

Issues Closed (partially resolved, re-open if still experiencing)

PRs Closed (superseded)

Azure PRs Merged (already tracked)

Net change: 13 issues closed, 6 PRs closed. All commented with resolution details.

@fabianwilliams Contributor Activity Update

Since this PR was opened, Fabian has been actively contributing across the OpenClaw codebase:

Approved & Merged

Reviewed / Commented

Closed

Summary: 4 PRs merged, 5 PRs reviewed/commented, 1 closed. Solid contributions across Teams integration, secrets handling, and cron infrastructure.

Update: Added Adaptive Cards PRs (6 total)

Added the full Adaptive Cards PR suite by @VikrantSingh01 to Section 2 (MS Teams Channel Plugin PRs):

Summary table updated: Teams PRs 46 -> 51, Total ~240 -> ~245.

Merge order: #41735 first (docs, approved, needs rebase) -> #41565 (core engine) -> #42307/#42304/#42350 (platform renderers, parallel) -> #41908 (docs, last).

Tracker Update (2026-03-26)

• Checked off [Bug]: OpenClaw WSL2 连接 Ollama 失败 #54498 ([Bug]: OpenClaw WSL2 Ollama connection failure) as resolved
• Added fix: WSL2 Ollama networking and provider discovery diagnostics #55435 (fix(plugins): WSL2 Ollama diagnostics) to WSL PRs section as merged

PR #55435 fixes the Ollama connection issue on WSL2 by disabling autoSelectFamily (Happy Eyeballs) to avoid IPv6 routing problems, and unwraps error.cause from undici's generic TypeError: fetch failed to surface real network errors.

📊 Tracker Update — March 26, 2026

New Issues Added (10)

New PRs Added (4)

Status Changes

• ✅ [msteams] Inline image downloads fail in 1:1 chats — inbound media uses bot adapter token instead of MSAL Graph token #28014 marked resolved (closed)
• ✅ fix(msteams): align feedback invoke authorization #55108 merged today — feedback invoke auth fix by @jacobtomlinson

Review Status

• fix(msteams): update FileConsentCard after user accepts upload #49580 — Approved, waiting on author rebase (merge conflicts)
• msteams: add reaction support with delegated auth and pagination helper #51646 — Approved, waiting on author rebase (merge conflicts)
• msteams: add message actions — pin, unpin, read, react, reactions #53432 — Under review

Notable Trend

The path-to-regexp v8 breaking change is now tracked across 6 issues + 4 PRs — this is the dominant P0 theme. Three competing fix approaches: SDK bump (#54866, #54965, #54424), dist patch (#54880), and Express 5 route fix (#55440).

2026-03-27 Session — @BradGroux

Merged tonight

Details

#56071 — When an agent uses tools mid-response (text > tool call > more text), streamReceivedTokens was a one-shot flag that never reset. Every text segment after the first tool call was silently dropped. Fix resets the flag and finalizes the stream so subsequent segments deliver via proactive fallback. 5 new tests.

#56134 — MSTeams was the only channel without blockStreaming config support. Added schema, wired disableBlockStreaming in the reply dispatcher, added blockStreamingCoalesceDefaults (minChars: 1500, idleMs: 1000), and enabled progressive flush during generation so blocks actually deliver mid-stream instead of batching until idle. 8 new tests.

Still open (identified as low-hanging fruit)

• P0: fix(msteams): prevent path-to-regexp crash with express 5 (#55161) #55440 — path-to-regexp crash fix (MERGEABLE, duplicates: msteams: bump @microsoft/teams.* to 2.0.6 to fix pathToRegexp error #54965, fix(msteams): patch Teams HttpPlugin /api* route pattern in dist #54880, msteams: bump @microsoft/teams.apps to 2.0.6 to fix pathToRegexp error #54866, chore(msteams): bump @microsoft/teams.apps&api from 2.0.5 to 2.0.6 #54424)
• P1: fix(msteams): prefer personal conversation in findByUserId to prevent DM misrouting #53458, fix(msteams): prefer freshest personal conversation for proactive DM sends #54702, fix(msteams): pass teamId and teamName to resolveAgentRoute() [AI-assisted] #50214 — DM routing fixes
• P2: fix(msteams): sanitize error messages sent to users (CWE-209) #33343 — sanitize error messages (CWE-209)
• P2: fix(msteams): clear pending upload timeout on removal #32555 — clear pending upload timeout

Quick status update on the recent MSTeams PRs:

• msteams: add member-info action #57528 reviewed, and merged.
• msteams: add channel-list and channel-info actions #57529 will be merged once rebased.
• msteams: add group management actions (add/remove participant, rename) #57530 reviewed and I left 1 inline comment. Main issue: removeParticipantMSTeams only checks the first page of Graph /members, so larger chats or channels can incorrectly report that a user is not a member. This one should not merge until pagination via @odata.nextLink is handled.

Net: 57528 merged, 57529 needs rebase before merge, 57530 needs a fix before merge.

Cleanup complete on stale Microsoft tracker items.

Closed in this pass:

• MSTeams: Image attachments not downloaded in bot DM chats (3 bugs) #24797
• [Bug]: Support request: Microsoft Teams channel setup fails on OpenClaw (Raspberry Pi) #17783
• [Bug]: Gateway JWT middleware blocks Bot Framework webhooks in msteams plugin #14436
• WhatsApp Channel Reliability Issues — Migration to Teams Graph #19908
• [Bug] SIGUSR1 restart on Windows creates orphaned process when running as Scheduled Task #23509
• Exec Tool on Windows does not capture stdout/stderr #21990
• Security: Insecure Default Tool Policies, Privilege Escalation, and Windows Command Injection #16323
• [Feature]: Windows support for obsidian skill #26160
• msteams: allow replyStyle config override for DMs #27765
• msteams: fix image download auth, double-counting, and typing indicator #26274
• fix(msteams): suppress reasoning-only text in outbound rendering #25511

Items already closed stayed marked resolved in the tracker.

April 1, 2026 - Session Summary

11 items resolved today (4 PRs merged, 5 issues closed, 1 PR closed as superseded, 1 dupe PR closed):

PRs Merged

Issues Closed (fixed by #55440)

• [Bug]: msteams plugin crash-loops due to path-to-regexp v8 incompatibility in @microsoft/teams.apps #55250, [msteams] path-to-regexp v8 breaking: /api* wildcard in Bot Framework CloudAdapter #54960, [msteams] Teams SDK migration breaks on path-to-regexp v8+ — /api* wildcard pattern rejected #54889, [msteams] Channel fails to start on 2026.3.24 — pathToRegexp "Missing parameter name at index 5: /api*" #54852, [Bug]: Teams Broken After 2026.3.24 udpates #54703 -- all path-to-regexp P0 duplicates

PRs Closed

• fix(msteams): patch Teams HttpPlugin /api* route pattern in dist #54880 -- superseded by fix(msteams): prevent path-to-regexp crash with express 5 (#55161) #55440
• fix(msteams): pass teamId into inbound route resolution #39352 -- superseded by fix(msteams): pass teamId and teamName to resolveAgentRoute() [AI-assisted] #50214

Contributor Updates

• slbteam08 (fix(msteams): pass teamId and teamName to resolveAgentRoute() [AI-assisted] #50214) -- first-time contributor, added to clawtributors

Running Totals

• MS Teams: 60/120 resolved (50%)
• Overall tracker: 86/353 resolved (24.4%)

Daily Progress — 2026-04-01

Issues Closed (7)

PRs Merged (2)

PRs Checked Off (1)

Tracker Totals

• Overall: 100/355 (28.2%)
• MS Teams: 74/122 (60.7%)
• Net items resolved today: 10

📋 Daily Update — 2026-04-02

Issues Closed (3)

PRs Merged (1)

Code review clean — thread suffix format correct, edge cases guarded, 21/21 msteams tests passed, pnpm check clean.

PRs Closed (2)

Tracker Housekeeping

• 13 new items added to tracker (8 issues + 5 PRs from April 2026)
• 27 stale items marked [x] via batch state-check (12 first pass + 5 P3s + 10 bulk audit)
• Summary: 139 closed / 228 remaining (up from 104 closed / 261 remaining at start of day)

Key Finding

PR #27224 (revoked-context proactive fallback, merged Mar 2) appeared lost from main, but was actually re-landed upstream as part of 866bd91c65 ("refactor: harden msteams lifecycle and attachment flows") with withRevokedProxyFallback extracted into its own module. Fork was 15k+ commits behind upstream — now synced.

Merged four Microsoft Teams PRs and closed their linked issues:

• fix(msteams): inject system event on message delivery failure #60430 -> closes [Bug]: msteams agent unaware of message delivery failure — silently drops errors #53911 (fix(msteams): inject system event on message delivery failure)
• fix(msteams): handle Adaptive Card Action.Submit invoke activities #60431 -> closes [msteams] Adaptive Card Action.Submit invoke activities silently dropped #55384 (fix(msteams): handle Adaptive Card Action.Submit invoke activities)
• fix(msteams): persist conversation reference during DM pairing #60432 -> closes [Bug]: MS Teams pairing drops first DM before saving conversation reference, so --notify always fails #43323 (fix(msteams): persist conversation reference during DM pairing)
• feat(msteams): add OpenClaw User-Agent header to Microsoft HTTP calls #60433 -> closes msteams: add OpenClaw User-Agent header to Microsoft backend HTTP calls #51568 (feat(msteams): add OpenClaw User-Agent header to Microsoft HTTP calls)

I also updated the tracker body to mark the four issues and four PRs as done and refreshed the Microsoft Teams summary counts.

Tracker update for recent Microsoft Teams merge work:

• Marked PR msteams: add channel-list and channel-info actions #57529 as done after merge.
• Marked issue [Feature]: Team Channels #52501 (Team Channels) as done to reflect the new channel-list and channel-info support.
• Updated the summary counts in the tracker body to keep the Microsoft totals in sync.

Merged PRs covered in this update:

• msteams: add channel-list and channel-info actions #57529 msteams: add channel-list and channel-info actions

Update rundown (last 24h) — closed/resolved items:

• ci: raise Windows checks timeout to 90 minutes #59647 — ci: raise Windows checks timeout to 90 minutes (closed)
• Windows: acpx plugin binary verification fails under Scheduled Task service #29305 — Windows: acpx plugin binary verification fails under Scheduled Task service (closed)
• [Bug]: acpx fails to spawn Claude CLI on Windows #50352 — [Bug]: acpx fails to spawn Claude CLI on Windows (closed)
• msteams: add typingIndicator config and prevent duplicate DM typing indicator #60771 — msteams: add typingIndicator config and prevent duplicate DM typing indicator (merged)
• msteams: Double typing indicator in Teams DMs #56380 — msteams: Double typing indicator in Teams DMs (closed via msteams: add typingIndicator config and prevent duplicate DM typing indicator #60771)
• Microsoft Teams: add config option to disable typing indicator before replies #60746 — Microsoft Teams: add config option to disable typing indicator before replies (closed via msteams: add typingIndicator config and prevent duplicate DM typing indicator #60771)
• [Feature] Simplify Teams integration for M365-only organizations (no Azure subscription) #7031 — [Feature] Simplify Teams integration for M365-only organizations (closed)
• [Bug]: Cross-channel reply context leak — Teams DM overwrites session reply target, causing heartbeat responses to route to wrong user #24148 — [Bug]: Cross-channel reply context leak — Teams DM overwrites session reply target (closed)
• [Feature]: Feature Request: Native Microsoft 365 integration (like gog for Google Workspace) #30023 — [Feature]: Native Microsoft 365 integration (closed)
• [Feature]: Microsoft Sharepoint and Openclaw #30299 — [Feature]: Microsoft Sharepoint and Openclaw (closed)
• DX Improvements for Windows/WSL2 Onboarding #7122 — DX Improvements for Windows/WSL2 Onboarding (closed)
• [Bug]: install on windows #25282 — [Bug]: install on windows (closed)
• Windows: exec tool creates visible console windows (conhost flash) #22851 — Windows: exec tool creates visible console windows (conhost flash) (closed)
• [Bug]: Error when installing via CMD on Windows 11 #5440 — [Bug]: Error when installing via CMD on Windows 11 (closed)

Summary: 14 resolved in the last 24h (13 closed + 1 merged PR).