OpenClaw published OpenClaw 2026.8.1-beta.3 early Monday, adding a broad beta package that touches model routing, setup flow, browser automation, gateway lifecycle management, backups, and channel plugin durability.
The release was published at 04:40 UTC on August 24, with npm and registry publication evidence attached to the GitHub release. It also confirms that all 89 official npm plugins were read back at 2026.8.1-beta.3 with beta selector and tarball integrity metadata.
That makes this more than a small patch release. It is a packaging checkpoint for several of OpenClaw's busiest runtime surfaces.
What Shipped
The headline item is model support. The release notes list GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support across both OpenClaw and the Codex runtime. The same release says @openclaw/codex@2026.8.1-beta.3 ships the managed @openai/codex@0.149.1 runtime.
For operators, the other practical highlight is SQLite backup and restore. OpenClaw now has compact, verified SQLite backup commands covering creation, listing, verification, and fresh-target restores. That matters because OpenClaw installations increasingly depend on durable local state for agents, channels, crons, task history, and session records.
The release also calls out:
- Control UI first-run setup continuing verified model setup into Custodian and optional channel setup.
- Puppeteer-compatible CDP relay support for paired Chrome sessions.
- Explicit external Gateway lifecycle supervision with verified restart handoff.
- Shared durable ingress monitors for channel plugins.
Browser And Gateway Changes
The CDP relay support is notable for teams using browser automation alongside paired Chrome sessions. The release says the relay now supports Puppeteer-compatible behavior, which should make external Chrome DevTools Protocol clients easier to connect without breaking the paired-browser model.
Gateway lifecycle also gets a more formal external-supervision path. The release describes explicit external Gateway supervision with verified restart handoff, a useful change for operators embedding OpenClaw inside a larger service manager or control plane.
Together, those changes point in the same direction: OpenClaw is becoming easier to run as infrastructure, not only as a local interactive assistant.
Publication Evidence
The release links to the npm package, registry tarball, tarball integrity hash, core npm preflight, core npm publication, and official plugin publication and reconciliation workflows.
That extra provenance matters for a beta with 89 official plugins in the loop. Plugin version skew can be hard to debug after an update, especially when channel plugins and runtime packages move together. The release page's read-back note gives operators a concrete verification point before they decide whether to test this beta.
Bottom Line
OpenClaw 2026.8.1-beta.3 is a substantial beta for people tracking the fast channel.
The biggest reasons to test it are GPT-5.6 reasoning support, verified SQLite backup workflows, better paired-browser automation, and the more explicit Gateway supervision contract. As usual for a beta, production operators should read the linked changelog and validation evidence before rolling it across critical agents.