Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu @all mentions silently dropped after PR #72658 — should be handled via prompt, not API-level block [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75001•Fetched 2026-05-01 05:39:09
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
2
Author
AxelHuAxelHu
Participants
AxelHuAxelHuclawsweeper[bot]clawsweeper[bot]
Timeline (top)
mentioned ×3commented ×1cross-referenced ×1

Root Cause

Commit b642ebece9 ("fix(feishu): do not treat @all as a bot mention") added isFeishuBroadcastMention checks to checkBotMentioned and extractMentionTargets. When Feishu sends an @all event, OpenClaw treats it as a broadcast and skips it entirely.

RAW_BUFFERClick to expand / collapse

Bug Description

After PR #72658 was merged (commit b642ebece9), OpenClaw's Feishu channel silently drops @all / @_all mentions at the API level — the bot never sees them, so it cannot respond even when responding would be appropriate.

Root Cause

Commit b642ebece9 ("fix(feishu): do not treat @all as a bot mention") added isFeishuBroadcastMention checks to checkBotMentioned and extractMentionTargets. When Feishu sends an @all event, OpenClaw treats it as a broadcast and skips it entirely.

Why This Is Wrong

  1. Wrong layer: Whether an agent should respond to @all is a behavioral decision that belongs in the agent's prompt/instructions — not in the channel API layer that receives events. Silently dropping @all means the agent loses all awareness of group-wide summons, which is a legitimate use case.

  2. Incomplete implementation: Our testing shows @all still triggers the bot in some cases (possibly because Feishu sometimes sends individual mention entries for each bot's open_id alongside the @all key, which isFeishuBroadcastMention doesn't filter). So the fix is both incorrect in design and inconsistent in behavior.

  3. Should be opt-in suppression via prompt: If the intention is "agents should not auto-reply to @all", the correct fix is to add a system-prompt instruction telling the agent to ignore @all mentions — not to strip them from the event before the agent ever sees them.

Expected Behavior

  • Bot should receive @all events normally (the mention should appear in context)
  • Agent should decide whether to respond based on explicit prompt instructions (e.g., "ignore @all mentions unless explicitly asked to respond")
  • Or alternatively: add a config flag feishu.suppressAllMentions: true that controls this behavior, rather than hard-coding it

Recommendation

Revert the isFeishuBroadcastMention silencing in checkBotMentioned / extractMentionTargets and handle @all suppression via the agent's prompt layer instead.

Environment

  • OpenClaw version: v2026.4.27 (clean-v4.27)
  • Channel: Feishu group chat
  • Related commit: b642ebece9 (fix #72658)

References

  • Commit that introduced this: b642ebece9
  • Related issue (different framing, same behavior): #74817

extent analysis

TL;DR

Revert the isFeishuBroadcastMention checks in checkBotMentioned and extractMentionTargets to allow the bot to receive @all events.

Guidance

  • Remove the isFeishuBroadcastMention checks to prevent silent dropping of @all mentions at the API level.
  • Handle @all suppression via the agent's prompt layer by adding instructions to ignore @all mentions unless explicitly asked to respond.
  • Consider adding a config flag feishu.suppressAllMentions: true to control this behavior instead of hard-coding it.
  • Verify the fix by testing the bot's response to @all mentions in a Feishu group chat.

Example

No code snippet is provided as the issue is more related to the design and implementation of the feature rather than a specific code block.

Notes

The current implementation is incomplete and incorrect, as it silently drops @all mentions and does not provide a consistent behavior. The proposed fix should be applied to ensure the bot receives @all events and can respond accordingly based on its prompt instructions.

Recommendation

Apply the workaround by reverting the isFeishuBroadcastMention checks and handling @all suppression via the agent's prompt layer, as this approach allows for more flexibility and control over the bot's behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#dependency error#configuration error#environment variable#network issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING