[BUG] Feishu messages doesn't show user_id of @ and msg sender

[Vast-Stars]

Quick Summary

飞书渠道看不到 被@ 用户的user_id和 发消息人的user_id

1. 被@的用户，在飞书消息里是删除了的

Feishu message received {sender_id=11111111111, chat_id=222222222, message_id=om_x100b55d8950148acb32e89c2f4a7b89, preview=给我和 拉个群}

2. 发言用户 user_id看不到

Environment & Tools

• PicoClaw Version: v0.2.0-347-gaaf99d7-dirty (git: aaf99d7)
• Go Version: go1.25.7
• AI Model & Provider: GLM-5 (or any)
• Operating System: macOS
• Channels: Feishu

❌ Actual Behavior

✅ Expected Behavior

能看到 信息发送人的user_id、被at人的id

💬 Additional Context

[Vast-Stars]

我打算自己修复。正在测试了

[Vast-Stars]

#1283

[nikolasdehor]

Looking at pkg/channels/feishu/feishu_64.go:

Issue 1 - @mention user_id stripped: In extractFeishuMessageContent (line 226-241), only the text field from the message JSON is extracted. Feishu's rich text format includes at elements with user IDs in the mentions array of the message event, but these are stripped when only text is parsed. The @user text is replaced by Feishu with the display name, losing the user_id.

The fix is to also parse the mentions field from the event message:

message.Mentions  // []EventMessageMention with Key, ID, Name, TenantKey

And either preserve the raw mention markup in the content or inject the user IDs as metadata.

Issue 2 - Sender user_id visibility: The extractFeishuSenderID function (line 208-223) does extract the sender's UserId, OpenId, or UnionId, and it's passed as senderID to HandleMessage (line 204). However, this ID is only logged (line 188-192) and set as SenderInfo.PlatformID — it's not necessarily visible in the agent's context.

PR #1283 (fix(feishu): preserve mention identity and sender open_id in messages) appears to address both issues. It likely preserves mention tags in the content text and ensures the sender's open_id is included in the message metadata so the agent can reference it.

[sipeed-bot]

@Vast-Stars Hi! This issue has had no activity for over 2 weeks, so I'm closing it for now to keep things tidy. If it's still relevant, feel free to reopen it anytime and we'll pick it back up.