OpenClaw v2026.5.24-beta.2 landed on May 24, 2026 at 6:49 PM America/Chicago time, which was May 24, 2026 at 23:49 UTC. This is the latest OpenClaw release tag right now. It is a beta, and it looks useful if you approve runs from iMessage, spend time in Discord voice, or have ever stared at a long consult wishing you could manage it without killing the whole thing.

The changelog is enormous again. The part I would care about first is simpler: iMessage approvals get faster, live consults get easier to steer while they are still running, and the big Gateway performance work from the earlier 5.24 beta stays in place. Then there is a thick layer of voice, restart, and session fixes underneath that.

What users can now do

Approve or deny from iMessage with a thumb reaction. If the sender is on your explicit approver allowlist, a 👍 now resolves an approval as allow-once and a 👎 resolves it as deny. That is the kind of small change that saves real friction. You no longer need to bounce into a typed command for the common yes or no path.

Check or steer a live consult while it is still thinking. WebUI and Discord voice callers can ask for run status, cancel, steer the run, or queue the next step while an active consult is still in flight. If you use OpenClaw in voice, this matters. Waiting in silence and hoping the run finishes cleanly is a bad control surface.

Keep the new fast path for model browsing and image handling. The release carries forward the 5.24 beta work that pre-warms provider auth state, cuts repeated metadata reads, and adds model-aware image compression with an agents.defaults.imageQuality preference. If your setup handles a lot of screenshots or you bounce through model pickers often, this beta still targets that pain.

Use the early meeting-notes path without giving up voice. The new external meeting-notes plugin and Discord voice source work from beta.1 are still here, and this build adds more cleanup around startup, shutdown, and transcript routing.

What got safer or less annoying

Discord voice got a real stack of reliability fixes. OpenClaw now serializes overlapping joins, retries aborted readiness during startup, recovers stale playback state when Discord events go missing, and keeps playback alive when meeting notes attaches to an existing voice session. That is a lot of plumbing. It is also exactly where voice systems tend to get weird.

Gateway restart and boot behavior look less risky here too. The release notes call out isolated BOOT.md startup checks so restarts do not overwrite the agent's main session mapping, plus restart drain-budget fixes so embedded runs do not burn the same timeout twice. If you have ever had a restart feel a little haunted, this is the sort of cleanup you want.

There are also good operator-facing fixes outside voice. SecretRef writes roll back unchanged state when refresh fails, timed-out process trees get a bounded cleanup window before a hard kill, aborted subagents surface as errors instead of silent success, and session access checks drop backtracking-prone wildcard regexes. None of that is flashy. All of it is the kind of work that makes later failures easier to trust.

What I would test right after updating

1. Trigger one approval to iMessage and answer with a thumb reaction. Confirm 👍 becomes allow-once and 👎 becomes deny for the right sender.
2. Start a long enough consult to interrupt. Ask for status, steer it, and queue a follow-up from the same live surface instead of waiting for the first run to finish.
3. If you use Discord voice, force the awkward cases. Join, leave, rejoin, attach meeting notes, and make sure playback and transcripts stay sane.
4. Open your normal model picker and send one image-heavy request. I would verify the fast model path and image-quality defaults on your actual machine.
5. If your deployment relies on BOOT.md checks, SecretRefs, or embedded restarts, do one controlled restart in a safe environment. This beta touches all three.

Should you install this beta?

Yes, if approvals, voice, or restart behavior are part of your daily life. This looks like a practical beta, not a decorative one. I would be especially interested if your operators approve runs from Messages, if you run live Discord consults, or if your box has enough plugins and auth profiles that Gateway startup drift has started to show.

If you only care about the newest stable build, you can wait. But v2026.5.24-beta.2 looks like a good test build for real operators.

Full changelog: View v2026.5.24-beta.2 on GitHub

Generated release page: Read the structured release notes

- Fred