OpenClaw v2026.5.20-beta.1: Discord, upgrade notes

v2026.5.20-beta.1 arrived on 2026-05-21 with a change that matters during maintenance: discord. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Before the package changes

01 / Discord

Source signal. let voice sessions follow configured Discord users into voice channels, with allowed-channel checks, multi-user handoff, bounded reconciliation, and DAVE recovery preservation.

Use Discord as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

02 / Discord/voice

Source signal. include bounded IDENTITY.md, USER.md, and SOUL.md profile context in realtime voice session instructions by default, with voice.realtime.bootstrapContextFiles: [] available to disable it.

The operator question around Discord/voice is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

03 / Dependencies

Source signal. bump the bundled Codex harness to @openai/codex 0.132.0 and refresh the app-server model-list docs for the new catalog.

Dependencies changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

04 / WhatsApp

Source signal. update Baileys to 7.0.0-rc12.

The operator question around WhatsApp is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Details behind the headline

Dependencies

update @openclaw/fs-safe to 0.2.7 so OpenClaw's default Python-helper-off policy keeps best-effort Node write fallbacks for private stores, secret writes, run logs, and media attachments on Linux/macOS.

Treat Dependencies as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Discord.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

WhatsApp. update Baileys to 7.0.0-rc12. Keep the reproduction and the post-fix result together in the acceptance record.

Dependencies. update @openclaw/fs-safe to 0.2.7 so OpenClaw's default Python-helper-off policy keeps best-effort Node write fallbacks for private stores, secret writes, run logs, and media attachments on Linux/macOS. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.20-beta.1 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.