[Bug]: Feishu channel: Message replies are routed to webchat instead of feishu #31859
Description
Bug type
Regression (worked before, now fails)
Summary
## Bug Report: Feishu Message Reply Routing Issue
### Description
When a message is received via the Feishu channel, it is correctly received and processed. However, the response is not sent back to Feishu, but is
incorrectly routed to webchat instead.
### Steps to Reproduce
1. Configure Feishu bot (App ID: `cli_a************`)
2. Send a message to the bot from Feishu
3. Message is received and processed
4. Reply does not appear in Feishu
### Expected Behavior
- Feishu message replies should be sent back to Feishu
- `messageChannel` should be `feishu`
### Actual Behavior
- Feishu message replies are sent to webchat
- `messageChannel` is set to `webchat` (should be `feishu`)
### Environment
- OpenClaw version: 2026.2.26
- Feishu configuration:
- `connectionMode: "websocket"`
- `dmPolicy: "pairing"`
- `pairingApproveCode: "********"`
- OS: Linux 6.6.87.2-microsoft-standard-WSL2
- Node: v24.14.0
### Log Evidencefeishu[default]: received message from ou_***************************** *** in oc_***************************** *** (p2p)
embedded run start: runId=... messageChannel=webchat ← Error: should be feishu
### Workaround
- Use the `message` tool to manually send Feishu messages (this works correctly)
- Replies appear in webchat instead
### Additional Information
- Sending Feishu messages via the `message` tool works correctly
- Issue only affects automatic reply routing
- Problem persists after restarting Gateway
Steps to reproduce
## Bug Report: Feishu Message Reply Routing Issue
### Description
When a message is received via the Feishu channel, it is correctly received and processed. However, the response is not sent back to Feishu, but is
incorrectly routed to webchat instead.
### Steps to Reproduce
1. Configure Feishu bot (App ID: `cli_a************`)
2. Send a message to the bot from Feishu
3. Message is received and processed
4. Reply does not appear in Feishu
### Expected Behavior
- Feishu message replies should be sent back to Feishu
- `messageChannel` should be `feishu`
### Actual Behavior
- Feishu message replies are sent to webchat
- `messageChannel` is set to `webchat` (should be `feishu`)
### Environment
- OpenClaw version: 2026.2.26
- Feishu configuration:
- `connectionMode: "websocket"`
- `dmPolicy: "pairing"`
- `pairingApproveCode: "********"`
- OS: Linux 6.6.87.2-microsoft-standard-WSL2
- Node: v24.14.0
### Log Evidencefeishu[default]: received message from ou_***************************** *** in oc_***************************** *** (p2p)
embedded run start: runId=... messageChannel=webchat ← Error: should be feishu
### Workaround
- Use the `message` tool to manually send Feishu messages (this works correctly)
- Replies appear in webchat instead
### Additional Information
- Sending Feishu messages via the `message` tool works correctly
- Issue only affects automatic reply routing
- Problem persists after restarting Gateway
Expected behavior
## Bug Report: Feishu Message Reply Routing Issue
### Description
When a message is received via the Feishu channel, it is correctly received and processed. However, the response is not sent back to Feishu, but is
incorrectly routed to webchat instead.
### Steps to Reproduce
1. Configure Feishu bot (App ID: `cli_a************`)
2. Send a message to the bot from Feishu
3. Message is received and processed
4. Reply does not appear in Feishu
### Expected Behavior
- Feishu message replies should be sent back to Feishu
- `messageChannel` should be `feishu`
### Actual Behavior
- Feishu message replies are sent to webchat
- `messageChannel` is set to `webchat` (should be `feishu`)
### Environment
- OpenClaw version: 2026.2.26
- Feishu configuration:
- `connectionMode: "websocket"`
- `dmPolicy: "pairing"`
- `pairingApproveCode: "********"`
- OS: Linux 6.6.87.2-microsoft-standard-WSL2
- Node: v24.14.0
### Log Evidencefeishu[default]: received message from ou_***************************** *** in oc_***************************** *** (p2p)
embedded run start: runId=... messageChannel=webchat ← Error: should be feishu
### Workaround
- Use the `message` tool to manually send Feishu messages (this works correctly)
- Replies appear in webchat instead
### Additional Information
- Sending Feishu messages via the `message` tool works correctly
- Issue only affects automatic reply routing
- Problem persists after restarting Gateway
Actual behavior
## Bug Report: Feishu Message Reply Routing Issue
### Description
When a message is received via the Feishu channel, it is correctly received and processed. However, the response is not sent back to Feishu, but is
incorrectly routed to webchat instead.
### Steps to Reproduce
1. Configure Feishu bot (App ID: `cli_a************`)
2. Send a message to the bot from Feishu
3. Message is received and processed
4. Reply does not appear in Feishu
### Expected Behavior
- Feishu message replies should be sent back to Feishu
- `messageChannel` should be `feishu`
### Actual Behavior
- Feishu message replies are sent to webchat
- `messageChannel` is set to `webchat` (should be `feishu`)
### Environment
- OpenClaw version: 2026.2.26
- Feishu configuration:
- `connectionMode: "websocket"`
- `dmPolicy: "pairing"`
- `pairingApproveCode: "********"`
- OS: Linux 6.6.87.2-microsoft-standard-WSL2
- Node: v24.14.0
### Log Evidencefeishu[default]: received message from ou_***************************** *** in oc_***************************** *** (p2p)
embedded run start: runId=... messageChannel=webchat ← Error: should be feishu
### Workaround
- Use the `message` tool to manually send Feishu messages (this works correctly)
- Replies appear in webchat instead
### Additional Information
- Sending Feishu messages via the `message` tool works correctly
- Issue only affects automatic reply routing
- Problem persists after restarting Gateway
OpenClaw version
OpenClaw version: 2026.2.26
Operating system
Linux 6.6.87.2-microsoft-standard-WSL2
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response