Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Environment:

• OS: Windows
• OpenClaw Version: 2026.4.14
• Feishu/Lark
  Bug Description:
  After upgrading from OpenClaw 3.28 to 4.x, group messages from a specific Feishu group (with requireMention: false configured) no longer reach the bot's session. The bot can:
• Send messages to the group (via cron jobs / message tool) ✓
• Receive direct messages (DMs) ✓
• But CANNOT receive any group messages ✗
  Steps to reproduce:

1. Configure a Feishu group with requireMention: false in openclaw.json
2. Have a cron job that sends to the same group (works fine)
3. Send any message or @mention the bot in the group - no response
   Expected behavior:
   With requireMention: false, the bot should respond to all messages in the group without needing an @mention. This worked correctly on OpenClaw 3.28.
   Actual behavior:

• Group messages are never received by the bot
• sessions_list shows no group session key (agent:main:feishu:group:<chat_id>)
• DM works normally
• Cron job pushes to group work normally
  Configuration:

"channels": {
  "feishu": {
    "connectionMode": "websocket",
    "groups": {
      "oc_xxx": {
        "requireMention": false
      }
    }
  }
}

Additional info:
The Feishu app's event subscription (im.message.receive_v1) is configured with "Long Polling" mode
All permissions are granted (im:message.group_at_msg:readonly, im:message.group_msg, etc.)
App version 1.0.4 published on 2026-04-07, bot worked normally before and after this date
The issue appeared sometime after 2026-04-07
Tried: changing requireMention, adding route bindings, upgrading/downgrading OpenClaw versions - none fixed the issue

### Steps to reproduce

/

### Expected behavior

/

### Actual behavior

/

### OpenClaw version

2026.4.14

### Operating system

Windows 11

### Install method

_No response_

### Model

minimax

### Provider / routing chain

Feishu / Long Polling (长连接)

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response