openclaw - 💡(How to fix) Fix Feishu channel: expose blockStreaming as a configurable option [1 comments, 2 participants]

Summary

The Feishu channel currently hardcodes disableBlockStreaming: true in the reply dispatcher. This means block-level replies (intermediate messages during agent execution) are never delivered incrementally — users only see the final response all at once.

Other channels like MS Teams already expose blockStreaming as a user-configurable option. It would be great to have the same for Feishu.

Current Behavior

In monitor.account-*.js:

return {
    dispatcher,
    replyOptions: {
        ...replyOptions,
        disableBlockStreaming: true,  // hardcoded
    }
};

When an agent produces multiple block replies, the Feishu user sees nothing until the final reply arrives. Combined with non-streaming models, this creates a poor experience where the user waits minutes with no feedback.

Desired Behavior

Add a blockStreaming (boolean) option to the Feishu channel config schema:

{
  "channels": {
    "feishu": {
      "blockStreaming": true
    }
  }
}

When enabled, block replies would be delivered as separate messages, giving users incremental progress during long agent runs.

Workaround

Currently the only workaround is manually editing the compiled dist file, which gets overwritten on every update.

Context

• OpenClaw version: 2026.5.2
• Feishu connection mode: websocket
• Model: non-streaming (free-tier OpenRouter), making this especially impactful