#OpenClaw’s discord replies are split at random points

1 messages · Page 1 of 1 (latest)

swift trellisBOT
#

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

charred lagoon
#

@peak tangle I was able to get it to not split the messages up, but only when enabling reasoning output into the discord chat.

peak tangleBOT
#

Yep — this usually isn’t the model itself, it’s Discord stream/chunk settings.

What you describe (short replies split, sometimes mid-word) is most often one of:

  • Discord preview streaming in block mode (channels.discord.streaming)
  • Block streaming enabled (channels.discord.blockStreaming / agents.defaults.blockStreamingDefault)
  • An unusually low textChunkLimit or aggressive draftChunk settings

Fast isolation test (2 minutes)

Turn streaming off first, then retest:

openclaw config set channels.discord.streaming off
openclaw config set channels.discord.blockStreaming false --strict-json
openclaw config set agents.defaults.blockStreamingDefault off
openclaw gateway restart
#

If splitting stops, we’ve confirmed it’s chunking/streaming config.

If you want, paste these and I can pinpoint the exact bad knob:

openclaw --version
openclaw config get channels.discord.streaming
openclaw config get channels.discord.blockStreaming
openclaw config get channels.discord.textChunkLimit
openclaw config get channels.discord.chunkMode
openclaw config get channels.discord.maxLinesPerMessage
openclaw config get channels.discord.draftChunk
openclaw config get agents.defaults.blockStreamingDefault
#

Nice find — that’s actually a really useful clue.

If enabling reasoning makes splitting disappear, this points to the Discord preview-stream/finalization path (not the model quality itself).
In 2026.3.12 that path can fall back to normal chunked send in some cases, which is where weird splits show up.

Practical workaround (without showing reasoning)

Keep reasoning the way you want, but force safer Discord delivery:

openclaw config set channels.discord.streaming off
openclaw config set channels.discord.blockStreaming false --strict-json
openclaw config set channels.discord.chunkMode newline
openclaw gateway restart

Quick confirmation

Reproduce once with reasoning off, while tailing logs:

# 
openclaw logs --follow

If you see something like:

  • discord: preview final edit failed; falling back to standard send

…that confirms this exact path.

If you want, paste openclaw config get channels.discord and I’ll sanity-check it line by line.
If this still happens after latest update, it’s worth filing a bug with logs: https://github.com/openclaw/openclaw/issues

Docs: