OpenClaw v2026.5.9-beta.1 landed on May 9, 2026 at 8:32 a.m. America/Chicago time, which was May 9, 2026 at 13:32 UTC. This beta has one change you should not sleepwalk through: the bundled BlueBubbles path is gone. If your iMessage setup still depends on channels.bluebubbles, stop and plan the migration before you update anything important.

If that does not apply to you, the release reads like solid operator cleanup. You get a clean way to clear temporary /think and /fast overrides, OpenClaw is better at telling you which model it is actually using, and a lot more CLI and auth failures now point you toward the next recovery step instead of dumping you into guesswork.

The iMessage break is real

The biggest practical item is the BlueBubbles removal. OpenClaw now expects iMessage setups to move to channels.imessage with imsg on a signed-in Mac, or through an SSH wrapper to a Mac if your main host is elsewhere. That is not a cosmetic rename. If you have an older BlueBubbles-backed config, you need to touch it.

I would treat this as a migration release first and a feature release second. If you run iMessage in production for a family inbox, a personal assistant, or anything that quietly needs to keep working, verify the new path before you roll the beta wide.

Temporary thinking overrides are easier to unwind

/think default and /fast default are small additions, but they fix a real annoyance. When you bump a session into a different reasoning or speed mode for one task, you can now drop back to the configured default without remembering the exact setting you started from.

/think default
/fast default

If you spend your day hopping between deep debugging and quick chat replies, this is the kind of command that saves friction every week. It also makes support and shared-agent situations less messy because "go back to normal" is finally a real command.

OpenClaw is getting better at saying what it is doing

This release pushes a lot of truth into the surfaces people actually use. Agents now get the current provider and model identity in their system prompt context, so "what model are you on?" has a better chance of getting the right answer from the runtime you are actually using. openclaw models status --check also does a better job honoring auth profile order, which matters if you juggle several credentials and were tired of health checks judging the wrong one first.

The CLI side picked up the same attitude. Parser, startup, config, guardrail, channel, task, and session failures now try harder to explain what broke and which recovery command to run next. That sounds boring until you hit a bad config late at night and the tool finally points you toward the fix instead of making you grep the docs.

There is a lot here for plugin-heavy and voice-heavy installs

The new optional oc-path plugin adds openclaw path for direct oc:// access to markdown, JSONC, and JSONL workspace files. That is useful if you script around OpenClaw or need surgical access to local project data without inventing your own wrapper.

There is also a broad catalog pass underneath image, video, music, and provider registration, plus a huge pile of Discord voice work. Realtime /vc modes, quieter consult handling, better permission probes, and faster ElevenLabs playback all landed in the same beta. If Discord voice is part of your stack, this is one of those releases that deserves a real sandbox session, not a skim.

Two host-level checks matter before you call this done

First, the supported Node 22 floor moved up to 22.16+. If you pin older Node 22 builds, check that now. Second, Docker runtime images now run under tini, which should help long-lived containers reap child processes and handle signals more cleanly. That is a quiet fix, but quiet is good when you are the one restarting containers.

What I would test right after updating

1. If you use BlueBubbles, migrate first. Move to channels.imessage, send a real message, and confirm inbound plus outbound behavior on the setup you care about.
2. Clear one temporary override on purpose. Run /think default or /fast default in a session where you had changed behavior and make sure it falls back the way you expect.
3. Ask the agent which model it is using. Then compare that answer with your actual configured route or session override.
4. Run openclaw models status --check. If you keep multiple auth profiles around, make sure the result matches the credential order you intended.
5. If you use Docker, restart once on purpose. If you pin Node manually, confirm you are at Node 22.16+ or on Node 24 before blaming the beta for a host mismatch.
6. If Discord voice matters to you, do one live room test. Beta notes this large usually hide at least one thing that only shows up with real microphones and real people.

Should you install this beta now?

Yes, with a plan, if you want the Discord voice work, better failure clues, cleaner auth checks, or an easier way to unwind session overrides.

Pause first if your iMessage path still runs through BlueBubbles or if your host is pinned to an older Node 22 build. Those are easy reasons to turn a nice beta into an annoying afternoon.

This is a useful beta. It just asks you to pay attention before you take the upgrade.

---

Full changelog: View v2026.5.9-beta.1 on GitHub

Generated release page: Read the structured release notes

- Fred