openclaw - 💡(How to fix) Fix streaming: partial sends first chunk as permanent message in 4.5 (Telegram) [2 comments, 1 participants]

Gateway log shows a single sendMessage ok during the affected window, but two messages visible in Telegram — suggesting the edit path is committing the draft prematurely rather than replacing it.

The issue appears to be triggered when config changes cause deferred gateway restarts while responses are in-flight, but also reproduces during normal stable operation after updating to 4.5.

TL;DR

Setting streaming to "block" and removing draftChunk configuration may resolve the issue of premature commitment of draft messages in Telegram.

Guidance

• Verify that the issue is specific to version 2026.4.5 by checking if the problem persists when downgrading to 2026.4.2.
• Check the gateway logs for any errors or warnings related to message editing or drafting during the affected window.
• Test the workaround provided in the issue by setting streaming to "block" and removing draftChunk configuration to see if it resolves the issue.
• Investigate the relationship between config changes, deferred gateway restarts, and in-flight responses to understand the root cause of the issue.

Example

{
  "channels": {
    "telegram": {
      "streaming": "block"
    }
  }
}

This configuration change may help resolve the issue by blocking streaming and removing the draft chunk configuration.

Notes

The issue may be related to changes in the streaming and draftChunk configurations in version 2026.4.5, and further investigation is needed to determine the root cause. The provided workaround may not be a permanent solution and may have unintended consequences.

Recommendation

Apply the workaround by setting streaming to "block" and removing draftChunk configuration, as it has been reported to resolve the issue in some cases. This change may help mitigate the problem until a more permanent solution is found.