Guide

OpenClaw v2026.5.20-beta.2: Discord, operator field notes

May 21, 20264 min readUpdated September 11, 2026By OpenClawBlog Team

The source record for v2026.5.20-beta.2 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

Channel
Pre-Release

Primary signals
Exec approvals; Discord; Discord/voice

Publication date
2026-05-21

A small field test

Exec approvals

Evidence from the release. remove the old cat SKILL.md && printf ... && <skill-wrapper> allowlist compatibility path so skill files must be loaded with the read tool and only the real skill executable is auto-allowed.

Operator reading. Read Exec approvals as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Discord

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

Operator reading. 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.

Discord/voice

Evidence from the release. 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.

Operator reading. 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.

CLI/tasks

Evidence from the release. include stale-running task maintenance decisions in openclaw tasks maintenance --json so retained and reconcile candidates explain backing-session, cron, CLI, and wedged-subagent state.

Operator reading. Keep CLI/tasks inside a test workspace until you can inspect its ledger, next run, failure state, and cancellation behavior from the operator surface.

The details that affect a runbook

Codex app-server

keep system-prompt reports working when bootstrap hooks provide workspace files with only a path and content, so hook-supplied SOUL/IDENTITY/TOOLS/USER context still reports injected characters correctly.

Check Codex app-server with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Operator checklist before rollout

Before touching persistent state, capture the version, host, provider, and workspace for Exec approvals.
Read the linked release record and verify a backup whenever the change can alter configuration or session data.
Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

CLI/tasks. include stale-running task maintenance decisions in openclaw tasks maintenance --json so retained and reconcile candidates explain backing-session, cron, CLI, and wedged-subagent state. Treat the fix as a boundary condition and retain the source wording beside your local result.

Codex app-server. keep system-prompt reports working when bootstrap hooks provide workspace files with only a path and content, so hook-supplied SOUL/IDENTITY/TOOLS/USER context still reports injected characters correctly. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.5.20-beta.2 source record; the release index and model provider reference remain the references to use for migrations and support boundaries.