Skip to content

OpenClaw 2.0 What's New: What Exactly Was Updated in v2026.8.1 ​

The conclusion first: "OpenClaw 2.0" is not a marketing slogan—it's an alias for the v2026.8.1 release—the official release notes' title says verbatim: "v2026.8.1 (AKA OpenClaw 2.0)". It is the largest single update in OpenClaw's history: 16,977 pull requests, 698 direct commits, and 987 contributors; the official blog post says it accounts for roughly half of all PRs ever merged in OpenClaw's history.

This lesson walks you through this major version using the official release notes: which 15 areas changed, which three changes most affect daily use, and what users on older versions should watch out for before upgrading. You can read along even without OpenClaw installed—the hands-on installation comes in the next lesson.

What You'll Be Able to Do After This Lesson ​

  • Explain in one sentence that "OpenClaw 2.0" = v2026.8.1, and how big this release is (16,977 PRs)
  • List the 15 areas covered by 2.0 per the official release notes, and know what changed in each area
  • Name the three upgrade points that most affect daily use: the brand-new Control UI, cross-session memory, and the end-to-end Skills chain
  • For users on older versions: know that you need to back up before upgrading, and that you can't downgrade directly afterward (sessions have moved into SQLite)
  • Distinguish the timeline after 2.0 and avoid being misled by packages like 2026.9.1-beta.1 that carry the wrong version label

Your Current Predicament ​

  • Articles that come up when you search "OpenClaw 2.0" tell different stories: some say it's just a UI revamp, others call it a whole new product—no one clearly explains what was actually updated
  • You see a string of version numbers like 2026.8.1, 2026.9.1, 2026.10.9 and don't know which one is "2.0", or which one you should install
  • You're on an older version (the Clawdbot / Moltbot era, or the 2026-year 6, 7 releases), afraid the upgrade will break things, but also afraid of missing new features if you don't upgrade

When to Use This Move ​

When you need to:

  • Decide "whether to upgrade / do a fresh install"—first see clearly what OpenClaw 2.0 changed and which part of your workflow it affects
  • Understand the release notes of subsequent versions (2026.8.2 → 2026.10.9)—they all build on the foundation laid by 2.0

And you don't want to:

  • Waste time on outdated tutorials and screenshots from the Clawdbot / Moltbot era
  • Discover only after upgrading that the session storage switched engines and you can't roll back

🎒 Preparation Before You Start ​

  • Finished reading OpenClaw What it is, and know what the terms Gateway, channel, and Claw refer to
  • This lesson is a version walkthrough: you can follow it even without OpenClaw installed, taking about 10 minutes; readers with an older version installed should focus on step 4
  • A browser at hand — step 2 requires checking against the original official release notes

Core Idea ​

**2.0 was made "accidentally". ** The official blog post "OpenClaw 2.0, Accidentally" (2026-08-30) tells the full story: it started with just two goals—simplifying installation and rebuilding the browser app as a first-class experience. But to do those two things thoroughly, the cleanup work had to run through the entire OpenClaw, changing things all the way down, until it finally grew into 2.0.

**It was also a "big-bang" release. ** The scale, verbatim from the release notes: "16,977 pull requests, 698 direct commits, and 987 contributors". The official blog post adds that before this, they had shipped 106 releases in 230 days, while this one went nearly seven weeks without a release—the team was reworking the product and the release process at the same time.

**The changes span 15 areas. ** Officially, the changes in 2.0 are broken into 15 sections, each with its own subpage (a user-readable change description + complete PR and commit records):

AreaOpenClaw 2.0 One-Sentence ChangeIn-Depth Course on This Site
Installation & OnboardingA clearer path from download to the first useful conversation; sessions and transcripts moved into SQLiteInstallation
Brand-new Web UIThe Control UI was rebuilt, putting conversations back at the centerControl UI
Updates & MaintenanceCheck the installation environment before updating; unsafe candidates are not swapped in, and the old CLI stays usableInstallation Troubleshooting
MessagingTelegram / Slack / Discord / native apps retain more conversation contextScenario Walkthroughs
MemoryA personal Claw can recall context across its own direct messagesMemory System
SkillsCreating, validating, installing, and invoking now form one chainGetting Started with Skills
Native AppsiPhone / iPad / Android / macOS / Wear OS all upgraded—
Models & ProvidersSelecting a model no longer waits for a full scan; requests are locked to the expected provider and account orderConnecting Models Overview
AutomationsScheduled tasks are now uniformly called Automations; openclaw cron keeps working as usualScheduled Tasks
Browser & Computer UseLogged-in sessions with an isolated managed profile or shared Chrome tabsBrowser Control
Plugins & IntegrationsAdmins can browse, install, enable/disable, and uninstall plugins in the Control UI—
Security & PrivacyApprovals are bound to the exact request, command, session, and person who handled itSecurity Hardening
Experience ImprovementsPast sessions are easier to find, long-task progress is visible, and cloud and paired-device sessions are supported—
Other Bug FixesCodex Well-scoped miscellaneous fixes covering Codex delegation, browser Talk, Doctor recovery, and more—
Maintainer Changes6,364 maintainer-facing changes (CI, tests, internal refactoring)Changelog

Three of these changes affect daily use the most—the brand-new Control UI, cross-session memory, and the end-to-end Skills chain—and Step 3 covers each one in detail.

Follow Along ​

Step 1: Confirm the version naming—OpenClaw 2.0 is v2026.8.1 ​

Why: If the version numbers don't match up, every tutorial you read afterward and every error you search for will be off.

Remember three points:

  • "OpenClaw 2.0" = v2026.8.1; the release notes title reads verbatim "v2026.8.1 (AKA OpenClaw 2.0)"
  • Release sequence: 2026.6.11 → 2026.7.1 → 2026.8.1(2.0) → 2026.8.2 → 2026.9.1…2026.9.9 → 2026.10.1…2026.10.9
  • This tutorial's baseline is v2026.10.9 (the current latest stable version); new installs all get versions after 2.0

Already have OpenClaw installed? Check the version in your terminal:

bash
openclaw --version

What you should see: The terminal prints the version number and exits. As long as it's ≥ 2026.8.1, you're in the world "after 2.0"; below it, you're still in the old world, and Step 4 is for you.

  • I've noted it down: 2.0 = v2026.8.1, tutorial baseline = v2026.10.9

Step 2: Go through the 15 areas of 2.0 against the official release notes ​

Why: Online retellings often omit things or exaggerate; the official release notes are the only authoritative list.

Open the official release notes:

text
https://docs.openclaw.ai/releases/2026.8.1

What you should see: It opens with the scale of the release (16,977 PRs / 698 direct commits / 987 contributors), followed by a list of 15 areas, each linking to its own subpage—where you'll find both user-facing change descriptions and complete PR and commit records.

Read it against the "Core Idea" table above: the left column lists the official areas, the right column the corresponding lessons on this site. Click into whichever lesson interests you; if you just want the highlights, continue to Step 3.

  • I've opened the official release notes and can point out the two or three areas I care about most out of 15

Step 3: Focus on the three new capabilities that most affect daily use ​

Why: It's normal not to remember all 15 areas, but almost every user touches these three daily.

Brand-new Control UI: conversations return to the center ​

In 2.0, the Control UI in the browser was rebuilt—the official positioning is "put conversations at the center of OpenClaw, with files, approvals, settings, and live work all revolving around the conversation." In terms of how it feels to use:

  • The sidebar lists conversations like ChatGPT / Claude, with the current conversation centered, instead of landing you on a separate Overview page first
  • New conversation is a proper settings page: before you start chatting you can pick the agent, model, reasoning effort, opening message or image, workspace, and which machine to run on
  • While working, tool calls and results appear in pairs; after a turn ends, the intermediate steps collapse into a "Worked for" summary and can be expanded again when needed
  • Want to bring up something off-topic? /btw opens a separate multi-turn side chat that doesn't interrupt the main task or pollute the main history

The Control UI is served directly by the Gateway at the default address http://<host>:18789/, and can be opened at any time with the openclaw dashboard command. For full usage, see Control UI.

Cross-conversation memory: your Claw remembers the private chats you two have had ​

Before 2.0, once a session was reset, what you had previously talked about was basically lost. From 2.0 onward, eligible personal Claws can recall relevant context from other private chats with the same agent—including what was last discussed before the reset. The boundaries are also clear:

  • Recall happens only between private chats with the same agent; groups, channels, and other agents never take part
  • Enabled by default for personal installs; disabled by default for installs with private-chat isolation configured, and explicit isolation configuration always takes priority
  • A single line of per-agent configuration controls it (rememberAcrossConversations):
json5
{
  agents: {
    entries: {
      personal: {
        memory: {
          search: {
            rememberAcrossConversations: true,
          },
        },
      },
    },
  },
}

The accompanying visible workflows are all in place: there's a Memory page in settings (status, search, browse), you can import existing memories from Claude Code, Codex, and Hermes, and openclaw memory forget can preview and clear derived memories per conversation. For details, see the memory system.

Skills as one chain: no more gaps from creation to invocation ​

2.0 links Skills' creation, validation, discovery, installation, and invocation into a single chain: creation goes through a guided flow, validators catch problems before writing (e.g., an overlong description), a bad skill fails on its own without dragging down other skills in the directory, and skills modified in a persistent session take effect on the next turn.

The Skill Workshop, meanwhile, brings proposals, checks, decisions, and application history into one workflow—how the skills Claw learned on its own were changed, and what you approved, are all traceable.

💡 A "Workshop 2.0" is still to come

Version history and Undo capabilities arrive in v2026.10.5 along with the "Skill Workshop 2.0". Don't mix up the timeline: the single chain is v2026.8.1 (OpenClaw 2.0), while version history + Undo is v2026.10.5. See Skill Workshop.

You should see: one sentence for each of the three capabilities—conversations back at the center (Control UI), private chats interconnected (cross-conversation memory), and skills as one chain (Skills). Each corresponds to a lesson on this site; dive in whenever you want to go deeper.

  • I can explain to others the boundaries of each of these three new capabilities (e.g., memory is only recalled within private chats with the same agent)

Step 4: Upgrading from an older version? Do two things before you start ​

Why: 2.0 migrated session and transcript storage into SQLite, and the official release notes include a dedicated downgrade warning—this is a "one-way door," so leave yourself a way back before going through it.

Do two things before upgrading:

  1. Create a verified backup. The official upgrade documentation requires creating one before updating, to protect a broader range of OpenClaw state.
  2. Do a dry-run rehearsal, without changing any configuration, handoff, or restart state:
bash
openclaw update --dry-run

You should see: the rehearsal outputs the upgrade path (checking Node compatibility, package manager ownership, etc.) without making actual changes. 2.0's update mechanism itself was reworked: unsafe candidates get blocked and the old CLI stays runnable; initiating an update in the Control UI first confirms the target, then shows progress and the final result.

After upgrading:

  • If you previously used the QMD memory engine, run openclaw doctor --fix—it removes the retired QMD settings, keeps compatible data, and rebuilds the index from Markdown
  • Want to downgrade back to the old file-storage version? You must first restore the archived old transcripts with the current CLI, and sessions created after the migration won't appear in the old version—if you can avoid downgrading, do

Readers who haven't installed OpenClaw can skip this step—the next lesson Installation installs a version from after 2.0 directly.

Checkpoint ✅ ​

  • I can state that "OpenClaw 2.0" = v2026.8.1, and the baseline for this tutorial is v2026.10.9
  • I can list at least three major changes in 2.0: the all-new Control UI, cross-session memory, and the Skills chain (or native apps, browser login-state sessions, approval security)
  • I know that 2.0 migrated session storage into SQLite: create a verified backup before upgrading, and restore the old transcript archive before downgrading
  • I know that 2026.9.1-beta.1 is a package with a mislabeled version (it actually corresponds to 2026.8.1-beta.4) and is not newer than the stable version 2026.8.1
  • I know where to check for later versions: the official releases page + this site's changelog

Pitfall warnings ​

❌ Treating 2026.9.1-beta.1 as a version newer than 2026.8.1 ​

The version note at the end of the official release notes says verbatim: the package released under the name 2026.9.1-beta.1 has a mislabeled version; it actually corresponds to 2026.8.1-beta.4 and is not newer than the stable 2026.8.1.

The right approach: judge old vs. new only by the release sequence (… → 2026.8.1 → 2026.8.2 → …), do upgrades uniformly via openclaw update, and don't manually pick packages with odd version numbers.

❌ Casually downgrading back to an old version after upgrading to 2.0 ​

Reason: sessions and transcripts have already been migrated into SQLite. The official warning: sessions created after the migration will not appear in the old version; before downgrading you must restore the archived old transcripts with the current CLI.

The right approach: create a verified backup before upgrading; if you truly must downgrade, first restore the old transcript archive per the official documentation, then change versions.

❌ Assuming cross-conversation memory will "remember all chats" ​

Keep the boundaries firmly in mind: recall happens only between private chats with the same agent; groups and channels are neither sources nor targets; other agents never take part; and explicit isolation configuration takes priority over everything.

Don't want this capability? Set the corresponding agent's rememberAcrossConversations to false, or keep the private-chat isolation configuration (off by default).

❌ Checking 2.0 against tutorials from the Clawdbot / Moltbot era ​

Commands, configuration fields, and interfaces from the old-name era largely stopped working after 2.0 (for example, session storage switched engines entirely). When you find old material, first check which version it targets before deciding whether to follow it. For version history, see the changelog.

Advanced tips (optional) ​

What else happened after 2.0? The timeline in one sentence:

VersionWhat to remember
2026.8.1OpenClaw 2.0, the star of this lesson
2026.8.2 → 2026.9.9A string of fixes and iterations after 2.0
2026.10.5Skill Workshop 2.0: skill version history + Undo
2026.10.9The baseline version for this tutorial

For the complete changes in each version, see the changelog: from OpenClaw 2.0 to 2026.10.9.

The official blog post is worth a read. "OpenClaw 2.0, Accidentally" (openclaw.ai/blog/openclaw-2-accidentally) not only tells the story of "how 2.0 was made by accident," it also mentions that shared cloud sessions turned OpenClaw into a multi-user team collaboration experience—the official team itself uses it to develop OpenClaw.

Command quick reference. The commands covered in this lesson (--version, update --dry-run, doctor --fix, dashboard, memory forget) are all collected in the CLI commands and configuration quick reference.

FAQ ​

Where is the official Clawdbot download, and how do I download it? ​

Clawdbot is the old name of OpenClaw; the product is now simply called OpenClaw, so don't look for a Clawdbot official site or installer anymore. For installation instructions, see the next lesson Installation: Get It Running in 5 Minutes with OpenClaw. New users installing fresh get versions after 2.0 (v2026.8.1) directly; this tutorial's baseline is v2026.10.9.

Can I download the official Clawdbot version and follow old tutorials alongside it? ​

Not recommended. Commands, configuration fields, and the interface from the Clawdbot / Moltbot era became largely invalid after 2.0 (for example, the session storage switched engines). When you find old materials, first check which version they target before deciding whether to follow them; for version history, see Changelog.

How do I install and manage Clawdbot plugins after 2.0? ​

Starting from OpenClaw 2.0 (v2026.8.1), administrators can browse, install, enable/disable, and uninstall plugins in the Control UI in the browser. The Control UI is served directly by the Gateway at the default address http://<host>:18789/, can be opened at any time with the openclaw dashboard command, and full usage is covered in Control UI.

Lesson summary ​

✅ The version terminology is clear: "OpenClaw 2.0" = v2026.8.1, a massive release with 16,977 PRs and 987 contributors; this tutorial's baseline is v2026.10.9.

✅ We went through 15 areas, three of which matter most day to day: the brand-new Control UI (conversations back at the center), cross-session memory (private chats with the same agent share context), and the Skills chain (create–validate–install–invoke).

✅ You now know the upgrade and version pitfalls: the SQLite migration is a one-way door—back up before upgrading and restore the archive before downgrading; 2026.9.1-beta.1 is the mislabeled package.

ConceptOne-sentence explanationWhere to go deeper
OpenClaw 2.0Alias for v2026.8.1, the largest single update in historyChangelog
Control UIA conversation-centered browser console, default port 18789Control UI
Cross-session memoryPrivate chats with the same agent can recall each other's contextMemory system
Skill WorkshopStores skill proposals, checks, decisions, and application historySkill Workshop
SQLite session migration2.0 onward, sessions and transcripts are stored in SQLite; downgrading requires restoring the archiveInstallation troubleshooting

Next lesson preview ​

With the version background covered, the next lesson gets hands-on: Installation: Get OpenClaw Up and Running in 5 Minutes.

You will learn:

  • Install OpenClaw with one command (the respective approach for macOS / Linux / Windows)
  • How Onboarding reuses your existing Claude Code / Codex login or API key
  • How to confirm the Gateway is alive once it's running
  • openclaw dashboard to open your own Control UI
gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.