Summary

Two Feishu DM messages from the bot owner were visible in Feishu message history but did not appear in the corresponding OpenClaw direct session JSONL and did not trigger a Merlin response.

This appears to be an inbound/routing/session-recording reliability issue for Feishu DMs, not an agent execution failure: the messages are retrievable from Feishu history, but no corresponding user turns were recorded in the OpenClaw session.

Environment

• OpenClaw runtime: 2026.5.22 (a374c3a in the installed runtime)
• Channel: Feishu / openclaw-lark loaded
• Gateway was otherwise healthy; Feishu group messages in the same period were received and processed.
• Affected surface: Feishu DM / direct conversation
• Bot account: default

Evidence

Feishu DM history contained these messages in chat oc_761ab096e17a317f220baac385dbcc88:

1. om_x100b6e5ca0db58a0c2aebab2103b6cc

   • Created: 2026-05-27T14:27:45+08:00
   • Content: control panel 的 worklfow 补全已经全部完成了吗？以后所有项目都可以复用了吗？如果是，那不是应该先做一个 wrapup 在回到 C18

2. om_x100b6e5dc5e9d480c3b37d4b078a268

   • Created: 2026-05-27T15:09:38+08:00
   • Same content.

Expected OpenClaw direct session:

session key: agent:main:feishu:direct:ou_a7afe17135735ff17d6bcb194b4875b2
session id: 87f84f23-5822-4218-ab43-3ffd493bb975
session file: /root/.openclaw/agents/main/sessions/87f84f23-5822-4218-ab43-3ffd493bb975.jsonl

The direct session did not contain either message id or the message text. The session updatedAt did not advance to those message times.

A Feishu group in the same runtime remained functional, which suggests this was not a global gateway/channel outage.

Expected behavior

A Feishu DM message that is visible in Feishu history and addressed to the bot should either:

• be admitted and recorded into the corresponding OpenClaw direct session, or
• be rejected with an explicit diagnostic/log reason (policy, allowlist, mention/admission, route mismatch, etc.).

Actual behavior

The DM messages were visible in Feishu history but missing from OpenClaw direct session records, and no visible response was produced.

Why this matters

From the operator/user perspective, this looks like the bot silently ignored a DM. It is difficult to distinguish from agent execution failure unless the operator manually compares Feishu history with OpenClaw session files.

Suggested investigation points

• Feishu DM chat id -> open_id direct-session mapping
• inbound claim / admission policy for DM messages
• direct conversation binding/session key resolution
• whether DM messages can be filtered before session write without diagnostic logging
• whether chat_id=oc_... DMs and open_id=ou_... sessions can diverge