Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Feishu bot can successfully receive and display outgoing messages (e.g., cron-generated AI daily headlines), but when a user replies to the bot in Feishu, OpenClaw does not process the incoming message — no agent response is generated.
Steps to reproduce
- Set up OpenClaw with Feishu channel configured (WebSocket mode).
- Send a scheduled/outbound message via cron or message tool to the Feishu user — message arrives successfully.
- Reply to the bot in Feishu DM (direct message).
- Observe: no agent turn is triggered, no response is generated in gateway logs, no reply message is sent back.
- Check gateway logs: there is no evidence of incoming message processing from the Feishu channel.
Expected behavior
When a user sends a message to the Feishu bot (DM), OpenClaw should process the incoming message through the agent pipeline and generate a response, just like it does on WebChat and other channels.
Actual behavior
No response from OpenClaw when replying to the Feishu bot. The outgoing messages (cron-scheduled or manually pushed) arrive successfully, but user replies are silently dropped. Gateway logs show no evidence of the incoming message being processed. This behavior is consistent across multiple attempts.
OpenClaw version
2026.6.5 (5181e4f)
Operating system
Linux 6.17.0-35-generic (Ubuntu)
Install method
npm global
Model
custom-ai-api-coregpu-cn/deepseek-v4-flash-w8a8 (default), also tested with glm-4.7-w8a8 on cron tasks
Provider / routing chain
openclaw -> custom-ai-api-coregpu-cn
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Relevant gateway log entries:
- plugins.entries.feishu: duplicate plugin id resolved (config-selected plugin overrides global)
- memory sync failed: No API key found for provider "openai" (may not be directly related)
- No "incoming message from Feishu" entries in gateway logs when user replies in Feishu DM
- Outgoing cron messages to Feishu are delivered successfully (logs show message delivery from cron jobs)
Impact and severity
Affected: Feishu users with dmPolicy set to allow DMs
Severity: High (blocks bidirectional communication entirely)
Frequency: Always reproducible (100% of attempts)
Consequence: Users can only receive pushed messages but cannot interact with the bot via Feishu. This makes the Feishu bot effectively write-only.
Additional information
Symptom: Feishu bot can push messages to user, but user replies are not processed. The plugin shows 'duplicate plugin id' warning which may be relevant. WebChat channel works fine for both sending and receiving. This suggests the issue is specific to Feishu channel inbound message routing, possibly related to the plugin conflict or event subscription not being properly received.
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Feishu bot can successfully receive and display outgoing messages (e.g., cron-generated AI daily headlines), but when a user replies to the bot in Feishu, OpenClaw does not process the incoming message — no agent response is generated.
Steps to reproduce
Expected behavior
When a user sends a message to the Feishu bot (DM), OpenClaw should process the incoming message through the agent pipeline and generate a response, just like it does on WebChat and other channels.
Actual behavior
No response from OpenClaw when replying to the Feishu bot. The outgoing messages (cron-scheduled or manually pushed) arrive successfully, but user replies are silently dropped. Gateway logs show no evidence of the incoming message being processed. This behavior is consistent across multiple attempts.
OpenClaw version
2026.6.5 (5181e4f)
Operating system
Linux 6.17.0-35-generic (Ubuntu)
Install method
npm global
Model
custom-ai-api-coregpu-cn/deepseek-v4-flash-w8a8 (default), also tested with glm-4.7-w8a8 on cron tasks
Provider / routing chain
openclaw -> custom-ai-api-coregpu-cn
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Affected: Feishu users with dmPolicy set to allow DMs
Severity: High (blocks bidirectional communication entirely)
Frequency: Always reproducible (100% of attempts)
Consequence: Users can only receive pushed messages but cannot interact with the bot via Feishu. This makes the Feishu bot effectively write-only.
Additional information
Symptom: Feishu bot can push messages to user, but user replies are not processed. The plugin shows 'duplicate plugin id' warning which may be relevant. WebChat channel works fine for both sending and receiving. This suggests the issue is specific to Feishu channel inbound message routing, possibly related to the plugin conflict or event subscription not being properly received.