openclaw - 💡(How to fix) Fix Feishu: mentionTargets auto-applied to all replies including error fallbacks, causes unintended cascade [3 comments, 1 participants]

When a Feishu group message @mentions multiple users (e.g. "@Alice @Bob @Carol"), the mentionTargets array is captured from the incoming message and unconditionally attached to every reply sent by the agent — including error fallback messages. 2. Agent's model run fails (e.g. API error, rate limit) 3. Error fallback text is generated (e.g. "⚠️ Missing API key...") 4. Reply is sent with @A @B @C automatically appended → all three users are notified of an error that doesn't concern them In extensions/feishu/src/reply-dispatcher.ts, the mentionTargets captured from the incoming message are passed into the deliver function and unconditionally applied as mentions: isFirst ? mentionTargets : undefined on every first text chunk — including error fallbacks. 3. Alternatively, only apply mentionTargets to non-error replies (requires distinguishing error fallbacks from intentional replies at the deliver layer).

TL;DR

Modify the reply-dispatcher.ts to stop passing mentionTargets to sendMessageFeishu/sendStructuredCardFeishu to prevent automatic @mentions in error fallback messages.

Guidance

• Review the reply-dispatcher.ts file to understand how mentionTargets are being passed to the deliver function and applied to every reply.
• Consider implementing a check to distinguish error fallbacks from intentional replies, and only apply mentionTargets to non-error replies.
• Update the System hint in bot.ts to indicate that mentionTargets are context-only and the agent should decide whether to include them in its reply.
• Test the changes to ensure that @mentions are no longer automatically appended to error fallback messages.

Example

// reply-dispatcher.ts
// ...
const isFirst = /* ... */;
const mentionTargets = /* ... */;
const reply = /* ... */;

// Only apply mentionTargets to non-error replies
if (!isErrorFallback(reply)) {
  deliver({ text: reply, mentions: isFirst ? mentionTargets : undefined });
} else {
  deliver({ text: reply });
}

Notes

The suggested fix requires modifying the reply-dispatcher.ts file and potentially updating the bot.ts file. The changes may have unintended consequences, such as breaking existing functionality or introducing new bugs.

Recommendation

Apply workaround by modifying the reply-dispatcher.ts file to stop passing mentionTargets to sendMessageFeishu/sendStructuredCardFeishu, as this is the most straightforward solution to prevent automatic @mentions in error fallback messages.