The OpenClaw 2.0 release moves your sessions into SQLite
OpenClaw 2.0 migrates AI agent sessions to SQLite, adds guided credential setup, and flags shared-session controls as not a security boundary.
OpenClaw 2.0, described as the largest update in the project's history, migrates sessions and transcripts into SQLite and adds guided setup that detects existing AI credentials from Codex, ChatGPT, Claude CLI sign-ins, API keys, and local Ollama or LM Studio models. The release expands multiplayer sharing while explicitly stating its permission controls are not tenant isolation or a security boundary, and that revoked access can briefly remain usable. Startup JavaScript requests fell from 140 to 45 and startup time from about 1.6 seconds to 575 milliseconds in simulated tests against a mocked Gateway. Automation wrappers must now inspect reported health because requesting --json does not waive risk acknowledgement.
- Sessions and transcripts now store in SQLite; downgrades require restoring legacy transcript artifacts via the current CLI.
- Guided setup verifies existing Codex, ChatGPT, Claude CLI, API key, Ollama, or LM Studio credentials before saving them.
- Shared session permissions are not tenant isolation; revoked access may appear active until the UI refreshes.
- Startup requests cut from 140 to 45 and startup time from 1.6s to 575ms in simulated tests.
- Unencrypted transcript snapshots in the browser profile are flagged for shared-machine threat modeling.
From the original article
2 min read at helpnetsecurity.com
OpenClaw is open source software that hands an AI model small standing jobs across your accounts, the kind of chore where it watches a mailbox for vendor advisories and pings you on Telegram when one names a product you run. OpenClaw 2. 0 is the largest update in the project’s history.
By @helpnetsecurity · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.