openclaw - 💡(How to fix) Fix [Bug]: Mattermost channel messages no longer received via WebSocket — regression in 2026.4.24 (DMs still work) [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

After upgrading from 2026.4.15 to 2026.4.24, the Mattermost plugin stopped receiving channel message events via WebSocket. DMs continue working normally — the bot responds to direct messages without any problem. The bug is specific to the channel inbound path.

This appears to be the same root issue previously reported in #11797 (closed as inactive). Per that issue's closing comment requesting a fresh report on the latest release, opening a new issue with current repro details and a clean version pinpoint.

Environment

• OpenClaw: 2026.4.24 (regression from 2026.4.15)
• Install method: npm global on macOS (Apple Silicon, M1 Ultra Mac Studio)
• Node: v25.6.1
• Service: LaunchAgent (ai.openclaw.gateway.plist)
• Mattermost: 10.11.15 (Team Edition), self-hosted in Docker on Synology DSM
• Network: nginx reverse proxy on Synology, no Cloudflare in front of Mattermost

Configuration

{
  "channels": {
    "mattermost": {
      "enabled": true,
      "baseUrl": "https://[redacted]",
      "botToken": "[redacted]",
      "dmPolicy": "allowlist",
      "allowFrom": ["[user_id]"],
      "groupPolicy": "allowlist",
      "groupAllowFrom": ["[team_id]"],
      "chatmode": "onmessage",
      "requireMention": false,
      "blockStreaming": false,
      "actions": { "reactions": true }
    }
  }
}

Verified to rule out config errors

• Bot is confirmed member of the test channel (verified via GET /api/v4/channels/{channel_id}/members)
• Bot token verified via direct GET /api/v4/users/me returning is_bot: true
• Config passes openclaw config validate cleanly
• Issue persists across full launchctl unload/load cycles and openclaw gateway restart
• Issue persists across regenerating the bot token

Diagnostic notes

The fact that DMs work but channel messages don't strongly suggests the WebSocket subscription itself is healthy and auth is good — events are flowing for at least one channel type. The bug appears specific to how non-DM channel events ("O" open, "P" private, "G" group) are subscribed to or dispatched in 2026.4.24.

Outbound delivery continues working throughout, so the bot's Mattermost API access is intact. Bug appears confined to the inbound WebSocket event subscription/dispatch path for non-DM channels.

I attempted to enable verbose logging for the Mattermost subsystem to capture more detail, but config.patch rejects logging.level as a protected path and I haven't found another runtime mechanism. If a maintainer can point me at the right env var or config path, happy to capture verbose logs and post them.

Suggested investigation

Given this is a clean regression from 2026.4.15 → 2026.4.24, a git log v2026.4.15..v2026.4.24 -- dist/extensions/mattermost/ src/extensions/mattermost/ should narrow this down quickly. If the source is in src/, that path may differ — adjust accordingly.

Related

• #11797 — same symptom, closed as inactive, original reporter never confirmed on latest release
• #11796 — silent WebSocket death (related but distinct: in my case the connection is healthy, just dispatching wrong)
• #65729 — broader Mattermost reliability concerns including WebSocket keepalive

Steps to reproduce

1. Run OpenClaw 2026.4.24 with Mattermost plugin enabled
2. Configure a bot account, add it to a channel
3. From a user account, post a message in that channel
4. Observe: no response, no log activity for that channel event
5. Send a DM to the same bot
6. Observe: DM works correctly, bot responds

Expected behavior

Bot receives channel message events and responds per chatmode setting, as it did in 2026.4.15.

Actual behavior

• WebSocket connects cleanly: mattermost connected as @timbot appears in log
• Outbound posting works (cron jobs deliver to channels successfully)
• DMs work end-to-end
• Channel messages produce zero log activity — no posted event, no policy decision logged, no error
• Bot status appears yellow/away in channels; never reacts, never responds

OpenClaw version

2026.4.24

Operating system

macOS 26.4.1

Install method

npm global

Model

anthropic/claude-opus-4.5

Provider / routing chain

openclaw -> anthropic

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response