openclaw - 💡(How to fix) Fix Mattermost streaming config: documented but not implemented + notification UX bug [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

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#71569Fetched 2026-04-26 05:11:22
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
commented ×1cross-referenced ×1

The Mattermost streaming configuration option is documented but not implemented. Additionally, the preview streaming behavior that does exist causes notification issues where users are alerted on draft creation but not when the final answer is ready.


Root Cause

Because the only available behavior is the old boolean blockStreaming, there is no way to:

  • Create drafts silently and only notify on final post
  • Or re-notify when the final answer is ready

Code Example

{
  "channels": {
    "mattermost": {
      "streaming": "partial"  // off | partial | block | progress
    }
  }
}

---

# Immediately after manual edit:
$ python3 -c "import json; c=json.load(open('openclaw.json')); print('streaming' in c['channels']['mattermost'])"
True

# After OpenClaw processes config:
$ python3 -c "import json; c=json.load(open('openclaw.json')); print('streaming' in c['channels']['mattermost'])"
False
RAW_BUFFERClick to expand / collapse

Summary

The Mattermost streaming configuration option is documented but not implemented. Additionally, the preview streaming behavior that does exist causes notification issues where users are alerted on draft creation but not when the final answer is ready.


Bug 1: streaming config key is silently discarded

Expected Behavior

Per documentation, channels.mattermost should accept:

{
  "channels": {
    "mattermost": {
      "streaming": "partial"  // off | partial | block | progress
    }
  }
}

Actual Behavior

  1. Adding "streaming": "partial" to openclaw.json saves successfully
  2. OpenClaw rewrites the config file and removes the streaming key entirely
  3. The old boolean "blockStreaming": false is the only recognized streaming-related key

Evidence

# Immediately after manual edit:
$ python3 -c "import json; c=json.load(open('openclaw.json')); print('streaming' in c['channels']['mattermost'])"
True

# After OpenClaw processes config:
$ python3 -c "import json; c=json.load(open('openclaw.json')); print('streaming' in c['channels']['mattermost'])"
False

Bug 2: Preview streaming creates notification UX problem

Current Behavior (with default/boolean streaming)

  1. User sends message → agent starts processing → draft preview post is created → user gets notification
  2. User opens app → sees incomplete thinking/tool output
  3. Final answer arrives as an edit to the same post → no new notification
  4. User misses the response or has to keep checking manually

Root Cause

Because the only available behavior is the old boolean blockStreaming, there is no way to:

  • Create drafts silently and only notify on final post
  • Or re-notify when the final answer is ready

Suggested Fixes

  • Option A: Implement the documented streaming key with partial/block/progress/off values
  • Option B: If keeping blockStreaming as fallback, add finalNotification: true to send a brief follow-up ping when the stream finalizes
  • Option C: Allow creating preview drafts silently (no notification) and only notify on the final post

Environment

  • OpenClaw version: v2026.4.23
  • Channel: Mattermost
  • Config: channels.mattermost with blockStreaming: false (old boolean, only available option)

Related

Previous issue with partial analysis: #71565 (superseded by this one)

extent analysis

TL;DR

Implement the documented streaming key with partial/block/progress/off values to fix the Mattermost configuration issue and notification problems.

Guidance

  • Verify the current behavior by checking if the streaming key is removed from the openclaw.json file after OpenClaw processes the configuration.
  • Test the old boolean blockStreaming key to understand its limitations and how it affects notification behavior.
  • Consider implementing one of the suggested fixes: Option A (implement streaming key), Option B (add finalNotification), or Option C (create preview drafts silently).
  • Check the OpenClaw documentation and version notes to see if there are any plans to implement the streaming key or address the notification issues.

Example

No code snippet is provided as the issue is related to configuration and documentation.

Notes

The issue is specific to OpenClaw version v2026.4.23 and the Mattermost channel. The suggested fixes may not be applicable to other versions or channels.

Recommendation

Apply workaround Option A: Implement the documented streaming key with partial/block/progress/off values, as it is the most straightforward solution to fix the configuration issue and notification problems.

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 Mattermost streaming config: documented but not implemented + notification UX bug [1 comments, 1 participants]