Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Long text messages (~3000 characters) cannot be sent to Discord through OpenClaw on version 2026.5.16-beta.3 (latest). Short messages still deliver normally, but longer assistant outputs fail to be delivered to the Discord channel.
Observed on 17 May 2026 in a test channel. The bot attempted to send a ~3000-character test reply and the message was truncated / not fully delivered.
Affected version:
- openclaw 2026.5.16-beta.3 (latest)
Channel: Discord
Steps to reproduce
- Run OpenClaw 2026.5.16-beta.3 connected to a Discord channel.
- Ask the bot to produce a long reply of around 3000 characters (e.g., "just send me something about 3000 characters, I want to test if openclaw can send long text to discord").
- Observe the bot's reply in the Discord channel.
Expected: The full ~3000-character message is delivered to Discord (chunked if needed, but complete).
Actual: The long message fails to send / is truncated; only a partial message appears in the channel.
Expected behavior
In a prior working version, OpenClaw delivered the full long reply to Discord, splitting into multiple messages if needed to stay within Discord's 2000-character message limit. The user should see the entire ~3000-character response posted in the channel.
Actual behavior
On openclaw 2026.5.16-beta.3, when the bot tries to send a ~3000-character reply to Discord, the message is not fully delivered. Only a partial/truncated message appears in the channel (e.g., the response visibly ends with "..." mid-thought, see attached screenshot), and the remaining content is dropped instead of being chunked and sent as follow-up messages.
OpenClaw version
2026.5.16-beta.3
Operating system
macOS 26.3
Install method
npm global (beta release)
Model
Any (model-agnostic — issue is in Discord delivery path, not model output)
Provider / routing chain
openclaw -> Discord (long-text/chunking path)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
- Affected users: anyone using OpenClaw 2026.5.16-beta.3 (latest) with a Discord channel.
- Frequency: reproducible whenever the bot's response exceeds Discord's single-message limit (~2000 characters).
- Severity: high for Discord users — any sufficiently long answer is silently truncated, so users lose information from the assistant.
- Practical consequence: long replies (summaries, code blocks, explanations) cannot be received in full on Discord, making the Discord channel unreliable for non-trivial outputs on this latest beta.
Additional information
This appears to be a regression on the latest 2026.5.16-beta.3 release. Earlier 2026.5.x releases handled long Discord replies correctly. Worth checking the Discord output / chunking code path on this beta.
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
Long text messages (~3000 characters) cannot be sent to Discord through OpenClaw on version 2026.5.16-beta.3 (latest). Short messages still deliver normally, but longer assistant outputs fail to be delivered to the Discord channel.
Observed on 17 May 2026 in a test channel. The bot attempted to send a ~3000-character test reply and the message was truncated / not fully delivered.
Affected version:
Channel: Discord
Steps to reproduce
Expected: The full ~3000-character message is delivered to Discord (chunked if needed, but complete).
Actual: The long message fails to send / is truncated; only a partial message appears in the channel.
Expected behavior
In a prior working version, OpenClaw delivered the full long reply to Discord, splitting into multiple messages if needed to stay within Discord's 2000-character message limit. The user should see the entire ~3000-character response posted in the channel.
Actual behavior
On openclaw 2026.5.16-beta.3, when the bot tries to send a ~3000-character reply to Discord, the message is not fully delivered. Only a partial/truncated message appears in the channel (e.g., the response visibly ends with "..." mid-thought, see attached screenshot), and the remaining content is dropped instead of being chunked and sent as follow-up messages.
OpenClaw version
2026.5.16-beta.3
Operating system
macOS 26.3
Install method
npm global (beta release)
Model
Any (model-agnostic — issue is in Discord delivery path, not model output)
Provider / routing chain
openclaw -> Discord (long-text/chunking path)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Additional information
This appears to be a regression on the latest 2026.5.16-beta.3 release. Earlier 2026.5.x releases handled long Discord replies correctly. Worth checking the Discord output / chunking code path on this beta.