OpenClaw 2.0 Moves Sessions to SQLite and Adds Sharing and Incognito Controls

· Original article ↗

Summary

OpenClaw 2.0 migrates sessions to SQLite and adds credential checks, shared cloud sessions, and incognito mode. The release warns that sharing is not isolation, incognito does not hide activity from providers or operators, and browser snapshots are unencrypted.

Key points

  • Sessions and transcripts now use SQLite; users should verify a backup before upgrading because downgrades require restoring legacy artifacts.
  • Setup checks existing AI credentials and tests the selected model before saving it; network installs that would expose OpenClaw without authentication are blocked.
  • Shared-session permissions are not tenant isolation or a security boundary, and revoked access may appear available until the UI refreshes or the Gateway rejects the action.
  • Incognito keeps conversations in process memory and skips normal transcript and automatic-memory storage, but providers, tools, and Gateway operators may still observe activity.
  • A bounded transcript snapshot used for faster startup is stored unencrypted in the browser profile.
  • Reported startup improvements were measured in a simulated test against a mocked Gateway, so they reflect reduced client activity rather than a general performance benchmark.

Article Details

Event Type
Software release
Impact
OpenClaw 2.0 migrates sessions and transcripts to SQLite and adds credential detection, shared-session controls, and incognito mode. Users should back up data before upgrading because downgrading requires restoring legacy transcript artifacts, and sessions created after migration will not appear in older builds. Shared-session permissions are not a security boundary or tenant isolation; incognito mode does not prevent model providers, tools, or Gateway operators from observing activity.

Products

Related Articles