openclaw - 💡(How to fix) Fix Feishu group chat replies=0: agent dispatches to wrong session (main webchat instead of agent session) [1 comments, 2 participants]

Problem

After upgrading to OpenClaw 2026.5.3+, Feishu group chat messages are received by the agent but no reply is sent back to Feishu.

Symptom: dispatch complete (queuedFinal=false, replies=0) — agent generates a reply (confirmed via session file) but Feishu channel receives nothing.

Environment

• OpenClaw 2026.5.4 (also reproduced on 2026.5.5-beta.1)
• macOS
• Node.js v23.11.0
• Feishu plugin: @openclaw/feishu v2026.5.4

Steps to Reproduce

1. Create a second agent (e.g., agent-B) in addition to main agent (agent-A)
2. Bind the Feishu bot to agent-B for group messages
3. Send a message in the Feishu group mentioning the bot
4. Bot receives the message and dispatches to correct session: agent:agent-B:feishu:group:[GROUP_ID]
5. But the agent actually runs in the main webchat session (sessionId=[SESSION_ID])
6. Reply never comes back to Feishu: dispatch complete (replies=0)

Log Excerpt

feishu[agent-B]: dispatching to agent (session=agent:agent-B:feishu:group:[GROUP_ID])  ← CORRECT
[trace:embedded-run] prep stages: runId=... sessionId=[SESSION_ID]  ← WRONG (main session!)
feishu[agent-B]: dispatch complete (queuedFinal=false, replies=0)

Direct messages (p2p) work fine — only group chats are affected.

Workarounds Tried

• groupSessionScope: \"group\" / \"group_topic\" — no effect
• renderMode: \"auto\" / \"raw\" — no effect
• streaming: false — no effect
• Cleared session files — no effect
• Multiple gateway restarts — no effect
• Downgrading to 2026.5.2 fixes the issue (but config compatibility prevents easy downgrade)

Suspected Root Cause

Session routing layer sends group messages to the correct agent session key, but the embedded run actually executes in the main webchat session instead. This is a regression introduced in 2026.5.3.