Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Microsoft Teams inbound messages stopped reaching OpenClaw after upgrading from 2026.4.9 to 2026.4.25/2026.4.26.

Outbound Teams sending still works, and Discord still works both directions. Downgrading to 2026.4.9 restores Teams replies.

Steps to reproduce

Reproduction steps

1. Run OpenClaw 2026.4.9 with Microsoft Teams configured.
2. Send a Teams DM or @mention the bot in a Teams group chat.
3. Confirm the agent replies.
4. Upgrade to OpenClaw 2026.4.26.
5. Send the same Teams DM or group @mention.
6. Observe no reply and no new OpenClaw log movement.
7. Downgrade to 2026.4.9.
8. Observe Teams replies working again.

Expected behavior

Teams DMs and @mentioned group messages should be received by OpenClaw and routed to the agent.

Actual behavior

Teams messages appear to never reach OpenClaw inbound handling/logging on 2026.4.25/2026.4.26.

OpenClaw version

• Broken: OpenClaw 2026.4.25 and 2026.4.26

Operating system

ubuntu 24

Install method

npm

Model

minimax

Provider / routing chain

minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Additional notes

This looks like a Teams inbound webhook/listener regression because there is no OpenClaw log movement when messages are sent, while outbound Teams sending still works.