- Media: treat `EPERM` from the post-write media fsync step as best-effort, allowing WebChat and channel uploads to finish on Windows filesystems that reject `fsync` after a successful write. Fixes #76844.

- Media/Telegram: send in-limit original images when optional image optimization is unavailable, so Telegram MEDIA replies and message-tool image sends do not fail just because `sharp` is missing. Fixes #77081. (#77117) Thanks @pfrederiksen.

- Diagnostics: include last progress, cron job/run ids, stopped cron job name, and the last assistant transcript snippet in stalled-session and stuck-session recovery logs so cron stalls show what was stopped.

- Streaming channels: add `streaming.preview.commandText: "status"` / `streaming.progress.commandText: "status"` to hide command/exec text in preview progress lines while keeping the released raw command text default. Fixes #77072.

- Agents/cron: let explicit cron `timeoutSeconds` drive both CLI no-output and embedded LLM idle watchdogs instead of being capped by resume defaults. Fixes #76289.

- Plugins/catalog: suppress missing `channelConfigs` compatibility diagnostics for external channel plugins that are disabled, denied, or outside a restrictive allowlist. Fixes #76095.

- Diagnostics: keep webhook/message OTEL attributes and Prometheus delivery labels low-cardinality and omit raw chat/message IDs from spans, so progress-draft and message-tool modes do not leak high-cardinality messaging identifiers.

- Google Meet: stop advertising legacy `mode: "realtime"` to agents and config UIs, while keeping it as a hidden compatibility alias for `mode: "agent"`, so new joins use the STT -> OpenClaw agent -> TTS path instead of selecting the direct realtime voice fallback.

- Google Meet: add `chrome.audioBufferBytes` for generated command-pair SoX audio commands and lower the default buffer from SoX's 8192 bytes to 4096 bytes to reduce Chrome talk-back latency.

953aece02c70b8df690b51e865a4aea838b53bbe9d43ef9495f80f719a831e38 config-baseline.json

2c78fb7af01e2ee9e919be5ab7b675347b36cae1e347f97fd2640a6f7c72f3ac config-baseline.json

31ec333df9f8b92c7656ac7107cecd5860dd02e08f7e18c7c674dc47a8811baa config-baseline.core.json

e10ba2f29f25fc665b96c714075af954eed686c56ca12783cf1f49498f86ac98 config-baseline.channel.json

606641569764473005f8343f4550500dcbe99cf54e1dc21960018cf455912196 config-baseline.plugin.json

cd7c0c7fb1435bc7e59099e9ac334462d5ad444016e9ab4512aae63a238f78dc config-baseline.channel.json

9832b30a696930a3da7efccf38073137571e1b66cae84e54d747b733fdafcc54 config-baseline.plugin.json

- `block` emits draft-sized chunks (use `draftChunk` to tune size and breakpoints, clamped to `textChunkLimit`).

- Media, error, and explicit-reply finals cancel pending preview edits.

- `streaming.preview.toolProgress` (default `true`) controls whether tool/progress updates reuse the preview message.

- `streaming.preview.commandText` / `streaming.progress.commandText` controls command/exec detail in compact progress lines: `raw` (default) or `status` (tool label only).

Hide raw command/exec text while keeping compact progress lines:

```json

{

"channels": {

"discord": {

"streaming": {

"mode": "progress",

"progress": {

"toolProgress": true,

"commandText": "status"

}

}

}

}

}

```

Preview streaming is text-only; media replies fall back to normal delivery. When `block` streaming is explicitly enabled, OpenClaw skips the preview stream to avoid double-streaming.

- `block`: append chunked preview updates.

- `progress`: show progress status text while generating, then send final text.

- `streaming.preview.toolProgress`: when draft preview is active, route tool/progress updates into the same edited preview message (default: `true`). Set `false` to keep separate tool/progress messages.

- `streaming.preview.commandText` / `streaming.progress.commandText`: set to `status` to keep compact tool-progress lines while hiding raw command/exec text (default: `raw`).

Hide raw command/exec text while keeping compact progress lines:

```json

{

"channels": {

"slack": {

"streaming": {

"mode": "progress",

"progress": {

"toolProgress": true,

"commandText": "status"

}

}

}

}

}

```

`channels.slack.streaming.nativeTransport` controls Slack native text streaming when `channels.slack.streaming.mode` is `partial` (default: `true`).

- `channels.telegram.streaming` is `off | partial | block | progress` (default: `partial`)

- `progress` keeps one editable status draft and updates it with tool progress until final delivery

- `streaming.preview.toolProgress` controls whether tool/progress updates reuse the same edited preview message (default: `true` when preview streaming is active)

- `streaming.preview.commandText` controls command/exec detail inside those tool-progress lines: `raw` (default, preserves released behavior) or `status` (tool label only)

- legacy `channels.telegram.streamMode` and boolean `streaming` values are detected; run `openclaw doctor --fix` to migrate them to `channels.telegram.streaming.mode`

Tool-progress preview updates are the short status lines shown while tools run, for example command execution, file reads, planning updates, or patch summaries. Telegram keeps these enabled by default to match released OpenClaw behavior from `v2026.4.22` and later. To keep the edited preview for answer text but hide tool-progress lines, set:

}

```

To keep tool-progress visible but hide command/exec text, set:

```json

{

"channels": {

"telegram": {

"streaming": {

"mode": "partial",

"preview": {

"commandText": "status"

}

}

}

}

}

```

For progress-draft mode, put the same command-text policy under `streaming.progress`:

```json

{

"channels": {

"telegram": {

"streaming": {

"mode": "progress",

"progress": {

"toolProgress": true,

"commandText": "status"

}

}

}

}

}

```

Use `streaming.mode: "off"` only when you want final-only delivery: Telegram preview edits are disabled and generic tool/progress chatter is suppressed instead of being sent as standalone status messages. Approval prompts, media payloads, and errors still route through normal final delivery. Use `streaming.preview.toolProgress: false` when you only want to keep answer preview edits while hiding the tool-progress status lines.

<Note>

- Telegram has shipped with tool-progress preview updates enabled since `v2026.4.22`; keeping them enabled preserves that released behavior.

- **Mattermost** already folds tool activity into its single draft preview post (see above).

- Tool-progress edits follow the active preview streaming mode; they are skipped when preview streaming is `off` or when block streaming has taken over the message. On Telegram, `streaming.mode: "off"` is final-only: generic progress chatter is also suppressed instead of being delivered as standalone status messages, while approval prompts, media payloads, and errors still route normally.

- To keep preview streaming but hide tool-progress lines, set `streaming.preview.toolProgress` to `false` for that channel. To disable preview edits entirely, set `streaming.mode` to `off`.

- To keep preview streaming but hide tool-progress lines, set `streaming.preview.toolProgress` to `false` for that channel. To keep tool-progress lines visible while hiding command/exec text, set `streaming.preview.commandText` to `"status"` or `streaming.progress.commandText` to `"status"`; the default is `"raw"` to preserve released behavior. This policy is shared by draft/progress channels that use OpenClaw's compact progress renderer, including Discord, Matrix, Microsoft Teams, Mattermost, Slack draft previews, and Telegram. To disable preview edits entirely, set `streaming.mode` to `off`.

- Telegram selected quote replies are an exception: when `replyToMode` is not `"off"` and selected quote text is present, OpenClaw skips the answer preview stream for that turn so tool-progress preview lines cannot render. Current-message replies without selected quote text still keep preview streaming. See [Telegram channel docs](/channels/telegram) for details.

Example:

Keep progress lines visible but hide raw command/exec text:

```json

{

"streaming": {

"mode": "partial",

"preview": {

"toolProgress": false

"toolProgress": true,

"commandText": "status"

}

}

}

}

}

```

Use the same shape under another compact progress channel key, for example `channels.discord`, `channels.matrix`, `channels.msteams`, `channels.mattermost`, or Slack draft previews. For progress-draft mode, put the same policy under `streaming.progress`:

```json

{

"channels": {

"telegram": {

"streaming": {

"mode": "progress",

"progress": {

"toolProgress": true,

"commandText": "status"

}

}

}

label: "Discord Draft Tool Progress",

help: "Show tool/progress activity in the live draft preview message (default: true). Set false to hide interim tool updates while the draft preview stays active.",

},

"streaming.preview.commandText": {

label: "Discord Draft Command Text",

help: 'Command/exec detail in preview tool-progress lines: "raw" preserves released behavior; "status" shows only the tool label.',

},

"streaming.progress.label": {

label: "Discord Progress Label",

help: 'Initial progress draft title. Use "auto" for built-in single-word labels, a custom string, or false to hide the title.',

label: "Discord Progress Tool Lines",

help: "Show compact tool/progress lines in progress draft mode (default: true). Set false to keep only the label until final delivery.",

},

"streaming.progress.commandText": {

label: "Discord Progress Command Text",

help: 'Command/exec detail in progress draft lines: "raw" preserves released behavior; "status" shows only the tool label.',

},

"retry.attempts": {

label: "Discord Retry Attempts",

help: "Max retry attempts for outbound Discord API calls (default: 3).",

);

});

it("can hide raw command progress text in Discord progress drafts by config", async () => {

const draftStream = createMockDraftStreamForTest();

dispatchInboundMessage.mockImplementationOnce(async (params?: DispatchInboundParams) => {

await params?.replyOptions?.onToolStart?.({

name: "exec",

phase: "start",

args: { command: "pnpm test -- --watch=false" },

detailMode: "raw",

});

await params?.replyOptions?.onItemEvent?.({ progressText: "done" });

return createNoQueuedDispatchResult();

});

const ctx = await createAutomaticSourceDeliveryContext({

discordConfig: {

streaming: {

mode: "progress",

progress: {

label: "Shelling",

commandText: "status",

},

},

},

});

await runProcessDiscordMessage(ctx);

expect(draftStream.update).toHaveBeenCalledWith("Shelling\n🛠️ Exec\n• done");

});

it("keeps Discord progress lines across assistant boundaries", async () => {

const draftStream = createMockDraftStreamForTest();

} from "openclaw/plugin-sdk/channel-reply-pipeline";

import {

formatChannelProgressDraftLine,

formatChannelProgressDraftLineForEntry,

resolveChannelStreamingBlockEnabled,

} from "openclaw/plugin-sdk/channel-streaming";

import { recordInboundSession } from "openclaw/plugin-sdk/conversation-runtime";

await maybeBindStatusReactionsToToolReaction(payload);

await statusReactions.setTool(payload.name);

await draftPreview.pushToolProgress(

formatChannelProgressDraftLine(

formatChannelProgressDraftLineForEntry(

discordConfig,

{

event: "tool",

name: payload.name,

},

onItemEvent: async (payload) => {

await draftPreview.pushToolProgress(

formatChannelProgressDraftLine({

formatChannelProgressDraftLineForEntry(discordConfig, {

event: "item",

itemKind: payload.kind,

title: payload.title,

import { logTypingFailure } from "openclaw/plugin-sdk/channel-feedback";

import { createChannelReplyPipeline } from "openclaw/plugin-sdk/channel-reply-pipeline";

import {

formatChannelProgressDraftLine,

formatChannelProgressDraftLineForEntry,

isChannelProgressDraftWorkToolName,

} from "openclaw/plugin-sdk/channel-streaming";

import {

if (!isChannelProgressDraftWorkToolName(payload.name)) {

return;

}

const statusLine = formatChannelProgressDraftLine(

const statusLine = formatChannelProgressDraftLineForEntry(

account.config,

{

event: "tool",

name: payload.name,