openclaw - 💡(How to fix) Fix Telegram: Final assistant reply appears above tool call progress messages (streaming mode) [1 comments, 2 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#77727Fetched 2026-05-06 06:22:22
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
3
Author
Timeline (top)
subscribed ×2commented ×1cross-referenced ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

Bug Description

In Telegram, when the assistant streams its response and makes multiple tool calls, the final reply sometimes appears above the intermediate tool call progress messages. This makes conversations confusing — the conclusion appears before the steps that led to it.

This was initially reported in #76529 and a fix was shipped in v2026.5.3 ("force a fresh final message when a visible non-preview bubble was delivered after the active answer preview"), but the issue is still reproducible on 2026.5.3-1.

Environment

  • OpenClaw: 2026.5.3-1 (2eae30e)
  • Channel: Telegram (direct)
  • Model: ollama/deepseek-v4-pro:cloud
  • OS: Linux (Debian 13, x86_64)

Steps to Reproduce

  1. Send a request that triggers multiple tool calls from the assistant
  2. Observe the streaming preview and tool call progress messages in Telegram
  3. Notice the final assistant reply appears above some of the tool call messages

Expected Behavior

The final assistant reply should appear after all intermediate tool call progress messages, in chronological order.

Actual Behavior

The final reply appears above tool call progress messages that were sent during the turn.

Video

https://streamable.com/h2knx6

Additional Context

This appears related to #76529 — the fix in v2026.5.3 may not fully cover all cases, or this may be a specific edge case where tool messages are delivered after the preview has already been replaced with the final answer.

Issue submitted by civil's clanker

extent analysis

TL;DR

Revisiting the fix implemented in v2026.5.3 to ensure it correctly handles all scenarios where tool call progress messages are delivered after the active answer preview may resolve the issue.

Guidance

  • Review the implementation of the fix in v2026.5.3 to identify potential gaps in handling tool call progress messages that arrive after the final answer preview.
  • Verify if the issue is specific to the Telegram channel or if it occurs across other channels as well, to determine if the problem is channel-specific.
  • Investigate the timing and sequencing of messages in the conversation to understand why the final reply is being placed above intermediate tool call messages.
  • Consider adding additional logging or debugging to track the order in which messages are received and displayed in the Telegram channel.

Example

No specific code snippet can be provided without more details on the implementation, but reviewing the code changes made in v2026.5.3 for the fix related to #76529 would be a good starting point.

Notes

The issue might be an edge case not fully covered by the previous fix, or there could be an interaction with other components or versions (like the model ollama/deepseek-v4-pro:cloud) that is causing the problem. Further investigation into the specifics of the tool call progress messages and how they are handled in relation to the final answer preview is necessary.

Recommendation

Apply workaround: Given the complexity and the fact that a previous fix did not fully resolve the issue, applying a workaround that ensures tool call progress messages are always displayed before the final answer preview might be necessary until a more comprehensive fix can be implemented. This could involve buffering messages or adjusting the display logic to prioritize chronological order.

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