openclaw - 💡(How to fix) Fix [Bug]: Feishu p2p DM dispatch crashes with TypeError: Cannot read properties of undefined (reading 'run') on 2026.5.27 (regression since 2026.5.22)

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

On 2026.5.27, inbound Feishu p2p (direct message) dispatch crashes before the agent runs. The gateway receives the DM, resolves the route to session=agent:main:main, then throws TypeError: Cannot read properties of undefined (reading 'run'). The agent never executes and no reply is sent. The same agent replies normally via the Slack channel and runs fine via embedded CLI, so this is isolated to the Feishu DM dispatch path. Downgrading to 2026.5.22 fixes it with no other changes.

Steps to reproduce

Steps to reproduce

1. OpenClaw 2026.5.27, Feishu channel enabled, connectionMode: websocket, dmPolicy: pairing.
2. Routing maps Feishu -> the main agent (no peer-scoped DM session override); DMs resolve to session=agent:main:main.
3. Send a p2p direct message to the bot from an already-paired user.
4. Gateway receives the message and attempts to dispatch.

Expected behavior

Expected behavior

Message is dispatched to the main agent and a reply is sent, as on 2026.5.22 and earlier.

Actual behavior

Actual behavior Dispatch throws; the agent never runs: [feishu] feishu[default]: received message from ou_xxx in oc_xxx (p2p) [feishu] feishu[default]: Feishu[default] DM from ou_xxx: hello? [feishu] feishu[default]: dispatching to agent (session=agent:main:main) [feishu] feishu[default]: failed to dispatch message: TypeError: Cannot read properties of undefined (reading 'run') On 2026.5.22 the same input produces: [feishu] feishu[default]: dispatching to agent (session=agent:main:main) [feishu] feishu[default]: dispatch complete (queuedFinal=true, replies=1) OpenClaw version Broken: 2026.5.27 (27ae826). Last known good: 2026.5.22. Operating system Ubuntu (systemd --user service) Install method npm (global) Model volcengine/ark-code-latest (provider-independent, see "What I ruled out") Provider / routing chain Not relevant to the bug; embedded run and Slack channel both work with the same agent/provider. Logs, screenshots, and evidence See "Actual behavior". The crash is reading 'run' at the Feishu dispatch step, before the agent runs. What I ruled out

Not session data: clearing the entire session store (~/.openclaw/agents/main/sessions) does not help; reproduces with sessions present, deleted, or empty. Not pairing: openclaw pairing list --channel feishu shows no pending requests; the DM reaches the dispatch step. Not a duplicate/stale Feishu plugin: ~/.openclaw/extensions is empty; Feishu is the built-in plugin. Not config: no sessionScope / sessionKey / DM-session override in the Feishu config. Not the agent runtime or provider: openclaw agent --agent main --message test returns a normal reply (embedded), and the same agent replies via Slack.

Impact and severity Feishu DMs are completely non-functional on 2026.5.27 for the DM -> main session routing. High for Feishu-only deployments. Additional information Narrow regression window: works on 2026.5.22, broken on 2026.5.27 (~5-day commit window). Likely area: Feishu DM dispatch / agent-runner resolution for the main session. Workaround: downgrade to 2026.5.22 (required OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 to run the older binary against config last written by 2026.5.27). Possibly related but distinct: #78417, #38686 (Feishu reply-drop, replies=0) and #18020 (Feishu DM dispatch TypeError, different missing symbol).

OpenClaw version

2026.5.57

Operating system

ubuntu 24.04

Install method

npm (global)

Model

deepseek v4 pro

Provider / routing chain

Not relevant to the bug; embedded run and Slack channel both work with the same agent/provider.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Logs, screenshots, and evidence
See "Actual behavior". The crash is reading 'run' at the Feishu dispatch step,
before the agent runs.
What I ruled out

Not session data: clearing the entire session store
(~/.openclaw/agents/main/sessions) does not help; reproduces with sessions
present, deleted, or empty.
Not pairing: openclaw pairing list --channel feishu shows no pending requests;
the DM reaches the dispatch step.
Not a duplicate/stale Feishu plugin: ~/.openclaw/extensions is empty; Feishu is
the built-in plugin.
Not config: no sessionScope / sessionKey / DM-session override in the Feishu
config.
Not the agent runtime or provider: openclaw agent --agent main --message test
returns a normal reply (embedded), and the same agent replies via Slack.

Impact and severity
Feishu DMs are completely non-functional on 2026.5.27 for the DM -> main session
routing. High for Feishu-only deployments.
Additional information
Narrow regression window: works on 2026.5.22, broken on 2026.5.27 (~5-day commit
window). Likely area: Feishu DM dispatch / agent-runner resolution for the main
session. Workaround: downgrade to 2026.5.22 (required
OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 to run the older binary against
config last written by 2026.5.27). Possibly related but distinct: #78417, #38686
(Feishu reply-drop, replies=0) and #18020 (Feishu DM dispatch TypeError, different
missing symbol).

Impact and severity

No response

Additional information

No response