openclaw - 💡(How to fix) Fix Slack: streaming preview completely silent when toolProgress: false — verbose mode broken since v2026.4.21 [4 comments, 3 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#74358Fetched 2026-04-30 06:24:59
View on GitHub
Comments
4
Participants
3
Timeline
9
Reactions
2
Timeline (top)
commented ×4subscribed ×2cross-referenced ×1mentioned ×1

Root Cause

Root cause hypothesis

Fix Action

Fix / Workaround

Steps to reproduce

  1. Configure Slack account with streaming: { preview: { toolProgress: false } } (workaround recommended in #71320)
  2. Set /verbose full in a Slack DM session
  3. Send any message that triggers multiple tool calls (file reads, bash, third-party API calls)

Workaround None. Both streaming: "off" and streaming: { preview: { toolProgress: false } } produce identical silent behavior.

Code Example

const previewToolProgressEnabled = Boolean(draftStream) && resolveChannelStreamingPreviewToolProgress(account.config);
// ...
const pushPreviewToolProgress = (line) => {
  if (!draftStream || !previewToolProgressEnabled || previewToolProgressSuppressed) return;
  // ...
};
const updateDraftFromPartial = (text) => {
  const trimmed = text?.trimEnd();
  if (!trimmed) return;
  previewToolProgressSuppressed = true; // <-- sets this to true
  // ...
  draftStream?.update(trimmed);
};
RAW_BUFFERClick to expand / collapse

Bug: Slack verbose mode produces no in-flight preview with streaming.preview.toolProgress: false (v2026.4.26)

Relates to: #71320 (partial fix), #69611 (introduced regression)

Environment

  • OpenClaw 2026.4.26
  • Channel: Slack socket mode
  • Verbose level: on and full
  • Config: channels.slack.accounts.<id>.streaming: { preview: { toolProgress: false } }

Steps to reproduce

  1. Configure Slack account with streaming: { preview: { toolProgress: false } } (workaround recommended in #71320)
  2. Set /verbose full in a Slack DM session
  3. Send any message that triggers multiple tool calls (file reads, bash, third-party API calls)

Expected Streaming draft preview should show partial reply text in the Slack message while tool calls execute — matching v2026.4.15 behavior.

Actual Nothing appears during tool execution. The final message only appears after all tool calls complete. Behavior is identical to streaming: "off" — zero in-flight feedback.

Root cause hypothesis

Looking at pipeline.runtime-C4g9nxhG.js in v2026.4.26:

const previewToolProgressEnabled = Boolean(draftStream) && resolveChannelStreamingPreviewToolProgress(account.config);
// ...
const pushPreviewToolProgress = (line) => {
  if (!draftStream || !previewToolProgressEnabled || previewToolProgressSuppressed) return;
  // ...
};
const updateDraftFromPartial = (text) => {
  const trimmed = text?.trimEnd();
  if (!trimmed) return;
  previewToolProgressSuppressed = true; // <-- sets this to true
  // ...
  draftStream?.update(trimmed);
};

When toolProgress: false, previewToolProgressEnabled = false. The onToolStart / onItemEvent callbacks call pushPreviewToolProgress() which returns early — correct. But then updateDraftFromPartial() sets previewToolProgressSuppressed = true expecting to suppress tool-progress lines that already appeared — but since none appeared, the net effect is just that draftStream never gets a meaningful update during the tool phase.

More critically: with suppressDefaultToolProgressMessages: previewToolProgressEnabled ? true : void 0, when previewToolProgressEnabled = false this becomes undefined, which may change upstream behavior around when onPartialReply fires.

Before v2026.4.21, the draft preview was driven purely by text streaming, independently of toolProgress. The coupling introduced in #69611 broke this separation.

Suggested fix previewToolProgressEnabled should gate only the tool-progress bullet lines (pushPreviewToolProgress). The updateDraftFromPartial / text streaming path should fire regardless. Specifically:

  • suppressDefaultToolProgressMessages should not depend on previewToolProgressEnabled
  • previewToolProgressSuppressed logic should not interfere with the base text-streaming path when toolProgress: false

Workaround None. Both streaming: "off" and streaming: { preview: { toolProgress: false } } produce identical silent behavior.

extent analysis

TL;DR

The issue can be fixed by decoupling the previewToolProgressEnabled flag from the updateDraftFromPartial text streaming path and ensuring suppressDefaultToolProgressMessages does not depend on previewToolProgressEnabled.

Guidance

  • Review the pipeline.runtime-C4g9nxhG.js file to understand how previewToolProgressEnabled affects the pushPreviewToolProgress and updateDraftFromPartial functions.
  • Modify the code to ensure updateDraftFromPartial updates the draftStream regardless of the toolProgress setting.
  • Investigate the impact of suppressDefaultToolProgressMessages being undefined when previewToolProgressEnabled is false and adjust the logic accordingly.
  • Test the changes with streaming.preview.toolProgress: false to verify that the draft preview is updated during tool execution.

Example

const updateDraftFromPartial = (text) => {
  const trimmed = text?.trimEnd();
  if (!trimmed) return;
  // Remove the line that sets previewToolProgressSuppressed to true
  // previewToolProgressSuppressed = true;
  draftStream?.update(trimmed);
};

Notes

The suggested fix requires careful consideration of the interactions between previewToolProgressEnabled, updateDraftFromPartial, and suppressDefaultToolProgressMessages. The changes should be tested thoroughly to ensure the draft preview behaves as expected with toolProgress: false.

Recommendation

Apply the suggested fix to decouple the previewToolProgressEnabled flag from the updateDraftFromPartial text streaming path, as this should resolve the issue without introducing new regressions.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Slack: streaming preview completely silent when toolProgress: false — verbose mode broken since v2026.4.21 [4 comments, 3 participants]