OpenClaw 2026.6.11: message-routing and reconnect fixes across chat channels
A reliability release aimed at misrouted replies, dropped sends and reconnect gaps across OpenClaw's chat integrations. Affects anyone running OpenClaw against Telegram, WhatsApp, Discord, iMessage, Matrix, Google Chat, Feishu, QQBot or Mattermost; no new capabilities, no config changes required.
PUBLISHED2026-06-30
OBSERVED2026-08-11
AGE1mo
SOURCES1
- Google Chat DMs no longer treated as group conversations; Space/group routing unchanged
- Discord, Telegram and WhatsApp replies stay bound to the intended conversation across retries, reconnects, session changes and group changes
- Background image/video/music results return to the requesting chat instead of failing or going to the wrong peer
- Telegram: quoted-message replies attach to the current question; native reactions no longer leak instructions; progress bubbles cleared before tool output; webhook survives channel restarts and config reloads
- Reasoning-model heartbeat checks no longer expose internal reasoning in channel output (opt-in Thinking messages still work)
- Matrix E2EE gateway memory leak fixed — previously grew until a crash took channels and in-flight work down
- iMessage: command-plus-link messages coalesce into one turn; stops replying to its own delayed echoes
- QQBot group admins can scope slash-command availability; private-only commands redirect to a private chat
- Feishu voice replies show audio duration
- Discord
message_tool_onlyturns no longer log a false failure on successful sends
COMMUNITY
No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.