You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- `progress` keeps one editable status draft and updates it with tool progress until final delivery
281
+
- `progress` keeps one editable status draft for tool progress, clears it at completion, and sends the final answer as a normal message
282
282
- `streaming.preview.toolProgress` controls whether tool/progress updates reuse the same edited preview message (default: `true` when preview streaming is active)
283
283
- `streaming.preview.commandText` controls command/exec detail inside those tool-progress lines: `raw` (default, preserves released behavior) or `status` (tool label only)
284
284
- legacy `channels.telegram.streamMode` and boolean `streaming` values are detected; run `openclaw doctor --fix` to migrate them to `channels.telegram.streaming.mode`
For progress-draft mode, put the same command-text policy under `streaming.progress`:
320
+
Use `progress` mode when you want visible tool progress without editing the final answer into that same message. Put the command-text policy under `streaming.progress`:
- short DM/group/topic previews: OpenClaw keeps the same preview message and performs the final edit in place
347
347
- long text finals that split into multiple Telegram messages reuse the existing preview as the first final chunk when possible, then send only the remaining chunks
348
+
- progress-mode finals clear the status draft and use normal final delivery instead of editing the draft into the answer
348
349
- if the final edit fails before the completed text is confirmed, OpenClaw uses normal final delivery and cleans up the stale preview
349
350
350
351
For complex replies (for example media payloads), OpenClaw falls back to normal final delivery and then cleans up the preview message.
0 commit comments