openclaw - 💡(How to fix) Fix [Bug] Feishu: p2p reactions routed to group session — chat_id oc_ prefix misidentified as group [1 participants]

Bug Description

Feishu p2p (direct message) reaction events are incorrectly routed to a group session instead of the user's direct session, causing the agent to respond in the wrong context or not respond at all.

Root Cause

Two issues in resolveReactionSyntheticEvent (source: extensions/feishu/src/monitor.account.ts):

1. Missing chat_type fallback

Feishu's WebSocket reaction events (im.message.reaction.created_v1) do not include chat_type. When fetchMessage also returns no chatType, the event is silently dropped:

const resolvedChatType = normalizeFeishuChatType(event.chat_type) ?? fallbackChatType;
if (!resolvedChatType) {
    // silently dropped — no fallback
    return null;
}

Fix: Add a fallback (e.g., default to "p2p") since most reaction scenarios are in direct messages.

2. p2p chat_id uses oc_ prefix, misrouted as group

Feishu assigns oc_-prefixed chat_id to both group chats and p2p conversations. The synthetic event passes this raw chat_id to session routing:

const syntheticChatId = syntheticChatIdRaw?.trim() ? syntheticChatIdRaw : `p2p:${senderId}`;

When a group session exists for that oc_ chat_id, the reaction gets routed there instead of the user's direct session.

Fix: When resolvedChatType is "p2p" or "private", force syntheticChatId to p2p:${senderId} regardless of the raw chat_id:

const syntheticChatId = syntheticChatIdRaw?.trim()
    ? (resolvedChatType === "p2p" || resolvedChatType === "private"
        ? `p2p:${senderId}`
        : syntheticChatIdRaw)
    : `p2p:${senderId}`;

Steps to Reproduce

1. Configure Feishu channel with reactionNotifications: "all" and connectionMode: "websocket"
2. Have both a p2p (direct) session and a group session active
3. In a p2p conversation, react to the bot's message with any emoji
4. Observe in gateway.log:
   • Before fix: skipping reaction XXXX on om_xxx without chat type context
   • After partial fix: reaction delivered to feishu:g-oc_xxx (group session) instead of feishu:direct:ou_xxx

Expected Behavior

p2p reactions should be delivered to the user's direct session (agent:main:feishu:direct:ou_xxx).

Environment

• OpenClaw: 2026.3.28 (also reproduced on 2026.3.31)
• Channel: Feishu, WebSocket mode
• Config: reactionNotifications: "all" at global and account level

Related

• #34528 (reaction message_id suffix causes 400 — separate but co-occurring issue)
• #33948 (add message reaction support)
• #31652 (support reaction event notifications)

Workaround

Patch dist/monitor-D9C3Olkl.js locally — see fix suggestions above.