OpenClaw v2026.10.10 moves your sessions between desktop and cloud

OpenClaw 2026.10.10 makes moving a session between your own machine and the cloud a first-class workflow. And cloud environments now know which repository you're working in.

Slide text

01 02 03 04 Desktop and cloud

openclaw/openclaw · CHANGELOG/2026.10.10.md

OpenClaw 2026.10.10 moves your sessions between desktop and cloud

Cloud environments now know your repository.

Starting a cloud environment takes less setup. The Node toolchain is verified, each repository can carry its own recipe, and profiles you save come back, with progress shown while it starts.

On the desktop, the Windows and Tauri apps can now start with a Gateway running on your own machine. A fresh macOS install walks you through dashboard setup instead.

The Control UI is rebuilt on a new architecture. Navigation shrinks to a compact rail, overlays and tabs are native Solid, and New conversation stays within reach.

Part two: agents and plugins.

Delegating to subagents got sturdier. Continuations stop crashing on conflicts, delegated work recovers after a restart, and a paused parent keeps the results its children send back.

Plugins can now act on a running agent. A plugin can fork the live context for a side question in the background, steer an active run, and set its own model fallbacks.

MCP apps from plugins now work across conversations. They reach workspace files too, through a relay bound to one principal. MCP events can trigger automations, and session hovercards show their schedules.

Running models locally? OpenClaw now manages llama.cpp for OCR, vision, and embedding-only setups. On first run it picks how to run inference for you, and providers report how long you're waiting.

Your phone does more as a node. Android adds system, photos, contacts, calendar and motion capabilities, and iOS gets an authenticated presence beacon that works in the background.

Part three: your data.

Backing OpenClaw up to Git no longer copies your secrets. PostgreSQL exports honor the exclude secrets option, plugin tokens, OAuth credentials and signing keys are redacted, and plugin state that isn't secret is kept.

Two limits. Secrets already committed stay in your Git history, because history isn't rewritten. And after you restore a redacted backup, the affected integrations have to sign in or register again.

If you keep OpenClaw's state in PostgreSQL, it now comes through backups and updates intact. OpenClaw checks for schema drift, ships migrations, and adds an experimental Workboard store.

Part four: fixes you may have hit.

If installs or updates broke on your Node version, they work again, from Node 24.16 and from Node 26.1. For security, Node 24.22.1 or 26.12.1 is still the one to run.

Streamed replies with tool-call XML no longer freeze the Gateway, and neither does long HTML that ends on a partial tag. Cron stops dropping missed slots, and the managed Codex CLI moves to 0.164.0.

The Android app sits this one out and stays on its August build. Every other change is in the release changelog. If you back OpenClaw up to Git, I'd update today for the redacted backups alone.