openclaw - 💡(How to fix) Fix [Bug] Telegram: text+exec in same response = message lost [1 comments, 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#59222Fetched 2026-04-08 02:27:20
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
closed ×1commented ×1locked ×1
RAW_BUFFERClick to expand / collapse

Bug Description

When assistant response contains both text and tool exec in same turn, text arrives but exec output is lost in Telegram.

Steps to Reproduce

  1. Configure streaming (any mode: off, partial, block, progress)
  2. Send message that triggers exec tool
  3. Response has text + exec in same message block
  4. Telegram receives only text OR nothing

Expected

  • Text only = arrives
  • Exec only = dont arrive
  • Text + exec same block = text arrive, exec hidden

Actual

  • Text only = arrives
  • Exec only = dont arrive
  • Text + exec same block = dont arrive in Telegram

OpenClaw Version

2026.4.1 (also reproducible on 2026.3.28 and 2026.3.31)

Model

MiniMax-M2.7 (NOT reproducible with Qwen3.5-122b or Qwen3.5-397b)

Configuration Tested

  • streaming: off/partial/block/progress
  • streamMode: off/partial
  • blockStreaming: true/false

Related

Issue #53384: streaming: partial drops text block when turn contains [thinking, text]

extent analysis

TL;DR

The issue may be resolved by modifying the message handling logic to properly handle cases where a response contains both text and tool execution output in the same message block.

Guidance

  • Investigate the message processing pipeline to identify where the exec output is being lost when sent alongside text in the same block.
  • Verify that the Telegram API is being used correctly to send messages with multiple components (text and exec output).
  • Check the differences in message handling between the MiniMax-M2.7 model and the Qwen3.5 models, as the issue is not reproducible with the latter.
  • Review the related Issue #53384 to see if there are any similarities or clues that could help resolve this issue.

Example

No code snippet can be provided without more context about the message handling logic.

Notes

The issue seems to be specific to the MiniMax-M2.7 model and the way it handles messages with both text and exec output. The fact that it's reproducible across different versions of OpenClaw suggests that the issue might be related to the model or the message handling logic rather than a version-specific bug.

Recommendation

Apply workaround: Modify the message handling logic to separate text and exec output into different message blocks or investigate alternative messaging formats that can handle multiple components correctly, as the current implementation seems to be model-dependent.

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 [Bug] Telegram: text+exec in same response = message lost [1 comments, 1 participants]