-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
Telegram partial streaming is noisy and slow for tool-heavy agent turns #77267
Copy link
Copy link
Open
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
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
2026.5.3-1{ "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:
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
offglobally 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:
offor final-only as the default for Telegram DMspartialas an explicit debug/power-user optionExpected 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.