Bug Description
BTW side questions get queued instead of being answered immediately when the main session is busy (Feishu regression)
Environment:
- OpenClaw: 2026.4.1 (also affected 2026.3.31)
- Channel: Feishu single chat (direct message)
- Introduced in: 2026.3.22, regressed in a later version
Steps to Reproduce
- Send a message to the bot in Feishu single chat
- While JAZZ is still generating the reply (stream not finished), send /btw
- Observe: the BTW message is silently queued — no immediate response
- Wait for the main session reply to finish
- Only then does the BTW answer appear
Expected Behavior
BTW answers return immediately as an ephemeral side result, without waiting for the main session to finish.
Actual Behavior
BTW message is treated as a normal queued message and only answered after the main session completes.
Additional Context
- This behavior worked correctly when BTW was first introduced in 2026.3.22
- The issue may be related to session routing changes in 2026.3.31: "Channels/session routing: move provider-specific session conversation grammar into plugin-owned session-key surfaces"
- Feishu does not appear in the official BTW-supported channel list (TUI, Discord, Telegram, WhatsApp are documented), but BTW did work correctly in 3.22 on Feishu
- TUI behavior: BTW works correctly (immediate response even when session is busy)
- The 2026.3.31 CHANGELOG also contains a BTW fix ("force /btw side questions to disable provider reasoning") which may have indirectly affected Feishu behavior
Severity
- Medium: BTW is still functional but degraded; users must wait for ongoing sessions to complete before getting BTW answers, breaking the side question UX contract
Bug Description
BTW side questions get queued instead of being answered immediately when the main session is busy (Feishu regression)
Environment:
Steps to Reproduce
Expected Behavior
BTW answers return immediately as an ephemeral side result, without waiting for the main session to finish.
Actual Behavior
BTW message is treated as a normal queued message and only answered after the main session completes.
Additional Context
Severity