Chunking/Truncation broken

[red storm]

I updated OpenClaw and on Discord, and for a long message, it didn't chunk anymore, it just sent one message ending with ... @ashen patio , how to fix?

[jolly parrot]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[ashen patio]

I checked current docs/source. Normal Discord sends still chunk at Discord’s 2000-char limit and also split tall replies with channels.discord.maxLinesPerMessage (default 17). So if you’re seeing one message ending in ..., it’s probably one of two things:

1. Streaming preview path is leaving you with the preview/truncated message instead of the final chunked reply. Quick workaround: turn Discord streaming off and restart the gateway.
2. Bound/focused Discord thread webhook delivery is being used. I found a likely regression there: bound-thread webhook sends can bypass the normal Discord chunker. Workaround: /unfocus that thread, or temporarily disable Discord thread bindings, restart, and retry.

Please grab the version first so we can avoid chasing the wrong build:

openclaw --version
openclaw status --all

Useful docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/channels/discord
https://docs.openclaw.ai/gateway/configuration-reference

[ashen patio]

If it’s the bound-thread/webhook case, this is issue-worthy: https://github.com/openclaw/openclaw/issues

[red storm]

it should be 2026.5.12.

[ashen patio]

Got it. If it’s really 2026.5.12, that lines up with a likely regression rather than an old install.

Can you try the two quickest isolations?

openclaw config set channels.discord.streaming off --strict-json
openclaw gateway restart

Then retry the long reply. If it still truncates, and this is a focused/bound Discord thread, run /unfocus in the thread and retry. The code path I’m suspicious of is bound-thread webhook delivery bypassing the normal Discord chunker.

Also please paste the literal output of:

openclaw --version
openclaw channels status discord

[ashen patio]

If confirmed, this should go to GitHub with those details: https://github.com/openclaw/openclaw/issues

[red storm]

"o" is not valid json.

[ashen patio]

Yep, my bad. With --strict-json, strings need JSON quoting.

Use this:

openclaw config set channels.discord.streaming '"off"' --strict-json
openclaw gateway restart

Or skip --strict-json:

openclaw config set channels.discord.streaming off
openclaw gateway restart

Thanks for catching that. 🦞

[red storm]

it mist be an object though???

[ashen patio]

You’re right. I checked the current schema: channels.discord.streaming is an object now. The docs example saying streaming: "off" is stale/confusing.

Use either of these:

openclaw config set channels.discord.streaming.mode '"off"' --strict-json
openclaw gateway restart

or set the whole object:

openclaw config set channels.discord.streaming '{"mode":"off"}' --strict-json
openclaw gateway restart

Sorry, that was two bad config commands in a trenchcoat. The actual shape is { mode, chunkMode, preview, block }.

[red storm]

turning streaming mode off works! i don't understand why this exist because discord doesn't support streaming.