Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Streaming cards don't send @mention notifications when agent writes <at> tags in text [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#73469•Fetched 2026-04-29 06:19:32
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
AxelHuAxelHu
Participants
AxelHuAxelHuclawsweeper[bot]clawsweeper[bot]
Timeline (top)
commented ×1cross-referenced ×1

Root Cause

  1. Streaming cards are created via POST /cardkit/v1/cards — a notification fires once at this point
  2. Content is updated via PUT /.../elements/.../content — this does NOT trigger notification re-sends
  3. streaming.close(text) receives only text content, no mentions array → Feishu has no mention data to trigger notifications
  4. Even if mentions were passed to close(), the streaming card API does not support sending a mentions list on close
  5. First-notification-only: Feishu sends notification only on card creation, not on subsequent element updates

Fix Action

Fix / Workaround

Current Workaround

Set streaming: false to fall back to non-streaming card/text delivery, which correctly triggers @mention notifications. However this removes the streaming experience entirely.

RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw feishu extension
  • Feishu streaming cards via Card Kit API (POST /cardkit/v1/cards, PUT /.../elements/.../content)
  • renderMode: "auto" or "card"

Problem

When an agent writes a <at user_id="OPEN_ID">name</at> tag in its response text, Feishu renders the mention in the card correctly, but the mentioned user receives no push notification. The message appears in the chat with the correct mention display, but no notification is sent.

Reproduction

  1. Bot receives a message in a group chat
  2. Bot replies using a streaming card that includes @someuser in the text
  3. The card renders with correct mention display, but the user receives no notification

Root Cause Analysis

  1. Streaming cards are created via POST /cardkit/v1/cards — a notification fires once at this point
  2. Content is updated via PUT /.../elements/.../content — this does NOT trigger notification re-sends
  3. streaming.close(text) receives only text content, no mentions array → Feishu has no mention data to trigger notifications
  4. Even if mentions were passed to close(), the streaming card API does not support sending a mentions list on close
  5. First-notification-only: Feishu sends notification only on card creation, not on subsequent element updates

Expected Behavior

When an agent includes <at user_id="...">name</at> in a response delivered via a streaming card, the mentioned user should receive a push notification, identical to how non-streaming text messages with <at> work.

Current Workaround

Set streaming: false to fall back to non-streaming card/text delivery, which correctly triggers @mention notifications. However this removes the streaming experience entirely.

Questions / Seeking Input

  • Is there a way to force-send a notification to a user when updating card content via the Card Kit API?
  • Is there a separate API to send mentions alongside a card reference message?
  • Has anyone found a pattern that supports both streaming cards AND @mention notifications?
  • Could the streaming card close() method accept a mentions parameter to re-trigger notifications?

Tags

feishu, streaming-card, mention-notification, cardkit

extent analysis

TL;DR

To fix the issue of missing push notifications for mentions in streaming cards, consider using the non-streaming card delivery by setting streaming: false as a temporary workaround.

Guidance

  • Review the Card Kit API documentation to see if there are any updates or new features that support sending notifications on element updates.
  • Investigate if there's a separate API or endpoint for sending mentions alongside a card reference message.
  • Consider reaching out to Feishu's support or developer community to see if anyone has found a pattern that supports both streaming cards and @mention notifications.
  • Evaluate the trade-offs of using non-streaming card delivery versus the benefits of streaming cards to determine the best approach for your use case.

Example

No code example is provided as the issue is more related to the API and its limitations rather than a specific code snippet.

Notes

The current workaround of setting streaming: false removes the streaming experience, so it's essential to weigh the importance of streaming cards against the need for @mention notifications. The Card Kit API's limitations and potential updates should be carefully considered.

Recommendation

Apply the workaround of setting streaming: false until a more suitable solution is found, as it currently ensures that @mention notifications are sent correctly, even if it means sacrificing the streaming experience.

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#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Streaming cards don't send @mention notifications when agent writes <at> tags in text [1 comments, 2 participants]