Description

When using Telegram streaming with verbose mode ON, each tool call causes previously streamed text to disappear. The text reappears later in a block below the last tool call output, but is now out of context — making it hard to follow the agent's workflow.

This is a regression or variant of #17935 (which was fixed in v2026.2.15 and closed on Feb 16, 2026).

Difference from #17935

• [Telegram] Streaming with extended thinking overwrites previous message text #17935 was specifically about extended thinking overwriting messages
• This issue occurs with verbose mode (/verbose on or verboseDefault: "on") and any tool call — no extended thinking required
• The text does eventually reappear, but displaced from its original position

Steps to Reproduce

1. Enable verbose mode: /verbose on (or set verboseDefault: "on" in config)
2. Set Telegram streaming to "progress" or "partial" (both affected)
3. Send a message that triggers multiple tool calls (e.g. "check all log files for errors")
4. Watch the Telegram chat during streaming

Observed Behavior

1. Agent streams text: "Lass mich die Logs checken..."
2. First tool call starts → text disappears
3. Tool call output appears
4. Agent streams more text → visible briefly
5. Next tool call → text disappears again
6. After all tool calls complete, the disappeared text reappears in a block at the end

The reappeared text is now out of its original workflow context, making it hard to follow what the agent did and why.

Expected Behavior

• Streamed text should remain visible when a tool call starts
• Text and tool call outputs should appear in chronological order
• The user should be able to follow the agent's workflow in real-time

Environment

• OpenClaw: v2026.3.2 (85377a2)
• Channel: Telegram (DM)
• Model: anthropic/claude-sonnet-4-5 (but likely model-independent)
• Streaming: "progress" (also observed with "partial")
• Verbose: ON (verboseDefault: "on")
• OS: macOS (ARM64) in UTM VM

Related

• [Telegram] Streaming with extended thinking overwrites previous message text #17935 — previous streaming overwrite issue (closed as fixed)

Workaround

• Set /verbose off (but loses visibility into agent actions)
• Disable streaming: "streaming": "off" (but loses real-time feedback)