Tutorial
For maintainers reading v2026.5.24-beta.2, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.
This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.
Channel
Pre-Release
Primary signals
iMessage; Gateway/perf; Gateway/update
Publication date
2026-05-24
Compatibility for maintainers
iMessage
Evidence from the release. support thumb-approval reactions ; thumb-up (Like tapback) resolves an approval as allow-once and thumb-down resolves as deny, with the explicit-approver allowlist read from channels.imessage.allowFrom; allow-always stays on the manual /approve <id> allow-always text fallback. Mirrors the WhatsApp behavior from #85477.
Operator reading. The useful evidence for iMessage is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.
Gateway/perf
Evidence from the release. reuse process-stable channel catalog reads, avoid repeated bundled-channel boundary checks, and rotate gateway watch CPU profiles so benchmark runs do not accumulate unbounded artifacts.
Operator reading. The operator question around Gateway/perf is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.
Gateway/perf
Evidence from the release. cache stable install-record, channel-catalog, bundled-channel, and Telegram session-store metadata during process-local hot paths to reduce repeated JSON and manifest reads.
Operator reading. For Gateway/perf, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.
Gateway/update
Evidence from the release. avoid fetching unrelated tags during dev-channel git updates so moved release tags do not block branch-based updates.
Operator reading. Gateway/update lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.
API, package, and test clues
CLI/update
suppress the expected future-config warning while an old update parent hands off to the freshly installed post-core process.
The promise in CLI/update is only useful if the old state returns. Take a verified backup, interrupt a candidate update, and inspect both the retained package and the service.
Run the smallest useful rehearsal
- Write down the baseline for iMessage, including the installed version, host, provider, and workspace.
- Confirm what can be restored, then take a verified backup before applying the candidate package.
- Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
- Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
- Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.
openclaw --version
openclaw gateway status
openclaw security auditLeave a usable maintenance note
Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.
Fix details to carry forward
Gateway/update. avoid fetching unrelated tags during dev-channel git updates so moved release tags do not block branch-based updates. This is the edge case to include in a regression check, especially when the release is pre-release.
CLI/update. suppress the expected future-config warning while an old update parent hands off to the freshly installed post-core process. Treat the fix as a boundary condition and retain the source wording beside your local result.
Keep the full v2026.5.24-beta.2 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.
Reference Trail
Sources and further reading
- full v2026.5.24-beta.2 notesgithub.com
- official release indexgithub.com
- channel routing guidedocs.openclaw.ai