diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index c2509f082..5f9b614e3 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "59c523c6b530224f55a5c00baca761563a180e4a",
-  "syncedAt": "2026-05-03T15:50:12.340Z"
+  "sha": "6becfcb27548f245f25d551839aba92e1deafef8",
+  "syncedAt": "2026-05-03T15:54:21.114Z"
 }
diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md
index b038818ed..551e49e83 100644
--- a/docs/channels/telegram.md
+++ b/docs/channels/telegram.md
@@ -307,7 +307,8 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"
 
     For text-only replies:
 
-    - short DM/group/topic previews: OpenClaw keeps the same preview message and performs a final edit in place
+    - short DM/group/topic previews: OpenClaw keeps the same preview message and performs a final edit in place, unless a visible non-preview message was sent after the preview appeared
+    - previews followed by visible non-preview output: OpenClaw sends the completed reply as a fresh final message and cleans up the older preview, so the final answer appears after intermediate output
     - previews older than about one minute: OpenClaw sends the completed reply as a fresh final message and then cleans up the preview, so Telegram's visible timestamp reflects completion time instead of the preview creation time
 
     For complex replies (for example media payloads), OpenClaw falls back to normal final delivery and then cleans up the preview message.