openclaw - 💡(How to fix) Fix Telegram partial streaming is noisy and slow for tool-heavy agent turns [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#77267Fetched 2026-05-05 05:50:22
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Timeline (top)
commented ×1

Telegram accounts configured with streaming.mode = "partial" can produce a very noisy and slow chat experience during tool-heavy turns. The user sees intermediate status/progress messages such as Process, Image Generation, and Exec updates that are not useful in normal Telegram usage.

Error Message

During a normal image-generation request over Telegram, the chat showed multiple intermediate messages before the final answer, including status/tool cards such as:

Root Cause

Telegram accounts configured with streaming.mode = "partial" can produce a very noisy and slow chat experience during tool-heavy turns. The user sees intermediate status/progress messages such as Process, Image Generation, and Exec updates that are not useful in normal Telegram usage.

Fix Action

Fix / Workaround

Environment

  • OpenClaw: 2026.5.3-1
  • OS: Windows 11 / win32
  • Channel: Telegram direct chat
  • Config before workaround:

Local workaround

Setting Telegram streaming to off globally and per account stopped the noisy partial updates:

Code Example

{
  "channels": {
    "telegram": {
      "streaming": { "mode": "partial" },
      "accounts": {
        "colorbestie": {
          "streaming": { "mode": "partial" }
        }
      }
    }
  }
}

---

Nautiling...
Process: ...

Nautiling...
Image Generation

Nautiling...
Exec: run python inline script ...
Exec: completed ...

---

{
  "channels": {
    "telegram": {
      "streaming": { "mode": "off" },
      "accounts": {
        "colorbestie": { "streaming": { "mode": "off" } }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Summary

Telegram accounts configured with streaming.mode = "partial" can produce a very noisy and slow chat experience during tool-heavy turns. The user sees intermediate status/progress messages such as Process, Image Generation, and Exec updates that are not useful in normal Telegram usage.

Environment

  • OpenClaw: 2026.5.3-1
  • OS: Windows 11 / win32
  • Channel: Telegram direct chat
  • Config before workaround:
{
  "channels": {
    "telegram": {
      "streaming": { "mode": "partial" },
      "accounts": {
        "colorbestie": {
          "streaming": { "mode": "partial" }
        }
      }
    }
  }
}

Observed behavior

During a normal image-generation request over Telegram, the chat showed multiple intermediate messages before the final answer, including status/tool cards such as:

Nautiling...
Process: ...

Nautiling...
Image Generation

Nautiling...
Exec: run python inline script ...
Exec: completed ...

This made Telegram feel extremely slow and cluttered. The user did not want or need these internal tool/status messages in the chat.

Local workaround

Setting Telegram streaming to off globally and per account stopped the noisy partial updates:

{
  "channels": {
    "telegram": {
      "streaming": { "mode": "off" },
      "accounts": {
        "colorbestie": { "streaming": { "mode": "off" } }
      }
    }
  }
}

Suggested improvement

Consider making Telegram default to final-only/no partial streaming, or adding a clearer doctor/setup recommendation for user-facing chat channels:

  • off or final-only as the default for Telegram DMs
  • keep partial as an explicit debug/power-user option
  • suppress tool lifecycle/status messages unless explicitly requested
  • provide a concise progress indicator that edits/deletes one status message instead of sending many separate messages

Expected behavior

For Telegram, normal agent turns should feel like a chat bot: minimal progress noise and a single useful final response, unless the user explicitly enables verbose/partial streaming.

extent analysis

TL;DR

Setting Telegram streaming to "off" globally and per account can prevent intermediate status messages and improve the chat experience.

Guidance

  • To mitigate the issue, update the configuration to set "streaming.mode" to "off" for both the global Telegram settings and the specific account settings.
  • Verify that the change takes effect by initiating an image-generation request over Telegram and checking if only the final response is displayed.
  • Consider adding a setup recommendation to default Telegram DMs to "off" or final-only streaming, reserving "partial" for explicit debug or power-user scenarios.
  • When implementing a progress indicator, ensure it edits/deletes a single status message instead of sending multiple separate messages to minimize noise.

Example

{
  "channels": {
    "telegram": {
      "streaming": { "mode": "off" },
      "accounts": {
        "colorbestie": { "streaming": { "mode": "off" } }
      }
    }
  }
}

Notes

This solution may not be suitable for users who require verbose or partial streaming for debugging purposes. In such cases, an explicit option to enable "partial" streaming could be provided.

Recommendation

Apply workaround: setting "streaming.mode" to "off" for Telegram, as it effectively prevents intermediate status messages and improves the chat experience.

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…

FAQ

Expected behavior

For Telegram, normal agent turns should feel like a chat bot: minimal progress noise and a single useful final response, unless the user explicitly enables verbose/partial streaming.

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 Telegram partial streaming is noisy and slow for tool-heavy agent turns [1 comments, 2 participants]