OpenClaw 2.0 Is Here: What's New, What Breaks, and What It Signals

§ 01The release in numbers

The announcement’s own framing is worth keeping: this was not a planned major version. The project’s velocity outgrew its foundation and its release process at the same time, and the team reworked both rather than shipping around the problem.

§ 02What’s actually new

Setup that starts with what you already have. Guided onboarding now detects AI access already on your machine: active ChatGPT or Claude subscriptions, API keys, and qualifying local Ollama or LM Studio models. It verifies that the exact chosen model can answer before saving it, then hands off to the rebuilt browser app, which opens directly into a conversation. Most configuration moved out of initial setup entirely; you finish configuring your Claw by talking to it.

Multiplayer, for real. Shared cloud sessions are the headline: team members can join an ongoing agent session, continue work where it left off, assign tasks to teammates with full context, and collaborate live. The OpenClaw team says it now uses this multiplayer mode to build OpenClaw itself. New team operator roles limit which agents and sessions each verified person can reach, and the docs are refreshingly honest about scope: these are collaboration controls, “not hostile-tenant isolation.”

Memory grows up. Built-in Memory now owns the core search and recall path, with the QMD add-on retired via a supported migration. Two defaults are worth noticing: background memory consolidation promotes provenance-qualified material into long-term memory (with a Dream Diary and an explicit off switch), and automatic self-learning can capture strong reusable lessons and turn them into proposed skills. There is also plain conversation search at last: find past conversations by exact words and reopen the surrounding messages.

Skills become a workflow. Skill Workshop connects the whole path: create a skill down a guided route, validate it before anything is written, find or install skills, call them from a conversation, and review proposed changes with an applied history. Invalid skills are now reported individually instead of breaking the catalog around them.

Widgets and dashboards. Chat can now hold interactive widgets, pin them to session dashboards, grant them specific actions or network origins, and export rendered views as images. Combined with durable session progress cards, the browser app is now a real control surface rather than a log viewer.

A more structural security model. This is the deepest change for anyone running OpenClaw seriously. Approvals now stay attached to the exact request, command, session, and person that received them. Reusable command permissions bind to exact arguments and a working directory, and script-backed commands recheck the reviewed bytes before running. Each session can choose read-only, guarded, workspace, or full access. A shared credential store keeps team-scoped secret values write-only, agents can request credentials through masked prompts that never enter model-visible text, and plugin installs from arbitrary executable sources now require an explicit force flag. After July’s advisory batch, this is the follow-through release: the trust boundaries the project promised are now load-bearing features rather than policy statements.

§ 03What breaks

Three migrations, all documented, plus one date to diary:

The pattern across all four is the same: openclaw doctor --fix is the recovery tool, and the release notes flag conflicts for operator repair instead of silently guessing.

§ 04What the release signals

OpenClaw 2.0 is a strong release, and the honest read is that it validates the direction this whole category is moving. A year ago, “personal agent” meant a chat loop with tools. The features that earned 2.0 status are all continuity features: memory that consolidates in the background, skills that accumulate from real work, permissions that persist across sessions, and shared context that survives a handoff between people. Those are the properties of a colleague, not a chatbot - the distinction we mapped in AI agent vs AI employee.

The difference is who operates it. OpenClaw is open source and self-hosted: you own the Gateway, the credential store, the upgrade path, and the security perimeter, and 2.0 makes each of those meaningfully better while leaving them yours to run. The announcement is admirably direct that this is the point: no company to trust, software you can shape and actually own. For tinkerers and teams with an operator’s mindset, that is the draw, and 2.0 lowers the cost of entry more than any release before it.

CellCog sits on the other side of the same conviction, so read our position with that declared: we build AI employees where the platform owns the perimeter, the memory architecture, and the upgrade path, and the two worlds already cooperate - OpenClaw agents have used CellCog as an execution layer for heavy deliverables since early 2026, and that path is unchanged in 2.0.

§ 05If you run OpenClaw today

The upgrade checklist, condensed from the release notes:

• Create a verified backup before upgrading; review the SQLite downgrade notes if you might roll back.
• Run openclaw doctor --fix after upgrading to migrate OpenProse, QMD memory settings, and legacy codex/* routes.
• Review the new per-session permission modes and set the narrowest that works; the least-privilege playbook applies directly.
• Check any external plugins against the September 1 SDK deprecation gates.
• Re-run your hardening pass: the July advisory checklist still applies, and 2.0’s new controls give it sharper teeth.

A release this size will shed follow-up fixes for weeks. When the notable ones land, this page gets the update, same day.