The open source AI agent OpenClaw has released v2026.8.1, informally known as OpenClaw 2.0. Despite arriving after a seven-week gap, it carries more than 16,000 merged pull requests and reworks nearly every part of the project, from installation and the chat interface to memory, skills and security. Anyone upgrading an existing install should read the migration notes before touching anything.

The Seven Quiet Weeks Went Into Rebuilding the Foundation

OpenClaw had previously shipped 106 releases in 230 days, most of them within a day or two of the one before. By that standard, seven weeks of silence was unusual. Development had not stalled. As the team grew, the volume and pace of work outpaced both the project's foundation and the process used to ship it, so both were reworked at the same time.

What piled up in the meantime amounts to roughly half of every pull request ever merged into OpenClaw. The release was built by 933 contributors, 569 of whom were contributing for the first time. The release notes count 16,304 analyzed pull requests and commits, broken down into 27 improvements or features, 196 bug and security fixes, 67 documentation changes, and 5,514 internal maintenance changes.

The Control UI Is Now Built Around the Conversation

The browser-based Control UI has been rebuilt to put conversations at the center. The separate Overview page that used to open on startup has been retired, leaving a conversation list in the sidebar and the active conversation in the middle, closer to how mainstream AI chat services are laid out.

There is also a way to keep side questions from derailing the work. Typing /btw opens a separate conversation so a tangent never lands in the main history. Workspace files can be edited straight from the file panel, a Changes panel shows branch commits, working-tree edits and pull request status, and a docked browser panel lets you navigate, click, type and annotate a screenshot before attaching it to the conversation. The file editor still cannot create or delete files, and Changes remains read-only.

The performance work comes with numbers. In a simulated default-chat test against a mocked Gateway with 50 milliseconds of latency, JavaScript requests fell from 140 to 45 and startup dropped from roughly 1.6 seconds to 575 milliseconds. Seven themes are built in, and 20 non-English Control UI locales are actively maintained.

Memory You Can Rewind, and Sessions You Can Invite People Into

Memory can now pull relevant context from the same agent's other conversations. Recall stays within the user's own private conversations. Groups, channels, other agents and deleted history are excluded, and an explicit direct-message isolation setting takes priority over everything else.

Because storage moved to SQLite, conversations can be rewound to any user message, forked from that point, and switched between preserved branches on web, macOS, iOS and Android. What rewinds is the transcript branch. Files that were already written and messages that were already sent do not roll back with it.

Shared cloud sessions add the other half of this: another person can be brought into work already in progress. The team says it used the feature to build this release, the point being that work can be handed over with its context intact.

Skill Self-Learning Comes With Clear Brakes

A new Skill Workshop pulls proposals, checks, decisions and applied history into a single flow. You can inspect the proposed instructions and supporting files, review results from plugin-provided scanners and graders, and then apply, reject or quarantine the proposal. Critical prompt-injection findings block application outright.

Self-learning has three settings. Off disables automatic repair, propose queues changes for review, and auto lets the Workshop create or update the skills it owns. New installations start in auto, while upgrades keep whatever they were already set to.

On the security side, a team-scoped Secret Store is new. It is worth noting that its values are not encrypted at rest and depend on the file permissions of OpenClaw's state directory, so it needs to be handled accordingly.

Migration Details Worth Checking Before You Upgrade

The largest incompatibility is that sessions and transcripts now live in SQLite. Downgrading to an older file-backed release requires using the current CLI to restore archived legacy transcripts first, and sessions created after the migration will not appear in older releases. A verified backup before upgrading is recommended.

Two deadlines apply. If your configuration still contains retired keys, the following command should be run before September 18, 2026.

openclaw doctor --fix

Separately, the beta.5 session-store bridge remains available through October 12, 2026.

There are a few smaller traps. Anyone running 2026.7.1 with pnpm 11 needs to run pnpm add -g openclaw@latest once, and OpenClaw does not upgrade Node on your behalf. Fresh CLI installs use Node 22.22.2. Known-vulnerable combinations of Node and SQLite now stop before state is opened.

Summary

OpenClaw 2.0 is a release that fixed the foundation before stacking on new features. Behind the visible changes, a conversation-first UI, rewindable memory and shared sessions, sits a storage format change and a set of dated migration tasks that matter more in practice. Starting fresh is clearly lighter than it was, but upgrading an existing install is best approached after a backup and a run of the doctor command.

The thumbnail image is AI-generated and for illustration only.