Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix QQ Bot plugin: Request option to restore streaming/chunked delivery (3.31 regression) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59742•Fetched 2026-04-08 02:41:04
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
bxy3045134656bxy3045134656
Participants
bxy3045134656bxy3045134656

Root Cause

I prefer streaming delivery because:

  1. User sees immediate feedback
  2. Better for long tasks (user knows progress)
  3. More natural conversation flow
RAW_BUFFERClick to expand / collapse

Feature Request: Restore Streaming Delivery for QQ Bot

Problem Description

In OpenClaw v2026.3.31, the QQ Bot plugin switched from streaming delivery to batched delivery:

Old behavior (pre-3.31):

  • Messages sent immediately as they are generated
  • User receives responses one by one in real-time
  • Better conversational experience

New behavior (3.31):

  • Messages cached during task execution
  • All messages sent at once after task completion
  • User must wait for entire task to finish

Impact

This affects:

  1. Cron scheduled tasks - User doesn't see progress
  2. Long-running tasks - Feels like the bot is unresponsive
  3. Conversational flow - Loses natural back-and-forth rhythm

Expected Behavior

Provide a configuration option to choose delivery mode:

json { "channels": { "qqbot": { "deliveryMode": "streaming" } } }

Options:

  • streaming - Send messages immediately (old behavior)
  • batched - Send all at once after completion (current 3.31 behavior)

Use Case

I prefer streaming delivery because:

  1. User sees immediate feedback
  2. Better for long tasks (user knows progress)
  3. More natural conversation flow

Environment

  • OpenClaw Version: 2026.3.31
  • OS: Windows 10.0.26200
  • Channel: QQ Bot
  • Plugin: @openclaw/qqbot v2026.3.31

Additional Context

This appears to be related to the new Background Tasks system introduced in 3.31. While batched delivery may work well for some use cases, streaming delivery should remain as an option.

Please consider adding this configuration option. Thanks!

extent analysis

TL;DR

Add a configuration option to choose between "streaming" and "batched" delivery modes for the QQ Bot plugin in OpenClaw.

Guidance

  • Review the Background Tasks system introduced in OpenClaw v2026.3.31 to understand how it affects message delivery.
  • Consider adding a "deliveryMode" configuration option for the QQ Bot plugin, allowing users to choose between "streaming" and "batched" delivery.
  • Evaluate the impact of streaming delivery on long-running tasks and conversational flow to ensure it aligns with the expected behavior.
  • Test the proposed configuration option with different use cases, such as cron scheduled tasks and long-running tasks, to verify its effectiveness.

Example

{
  "channels": {
    "qqbot": {
      "deliveryMode": "streaming"
    }
  }
}

This example illustrates the proposed configuration option for enabling streaming delivery.

Notes

The feasibility of implementing this feature request depends on the underlying architecture of the Background Tasks system and the QQ Bot plugin. Further investigation is necessary to determine the potential challenges and limitations of adding this configuration option.

Recommendation

Apply a workaround by adding a custom configuration option to the QQ Bot plugin, allowing users to choose between "streaming" and "batched" delivery modes. This approach provides a flexible solution for users who prefer the old behavior while maintaining the current functionality for those who prefer batched delivery.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#network issue#logging issue#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING