OpenClaw 2.0 adds shared cloud sessions and detects existing AI subscriptions

OpenClaw released version 2.0 of its open-source personal AI agent on 30 August 2026. The project says the release took nearly seven weeks, its longest development cycle, and drew work from 933 contributors across more than 16,000 pull requests. The project says that is roughly half of every pull request ever merged into OpenClaw. InfoQ covered the release on 1 September.

The setup change

The first thing 2.0 changes is how a new install starts. Instead of asking for API keys up front, the installer looks at what is already on the machine. The project writes that "installation was the first place we needed to make OpenClaw easier, so for first-time installs we are starting with what is already on someone's computer." In practice that means it detects an existing ChatGPT or Claude subscription, keys that are already present, and models installed locally.

The browser application has been rebuilt as the main way people use it. Earlier versions treated the browser as a secondary control screen next to the terminal. In 2.0 it is where the first conversation happens and where configuration, task monitoring, and workflow interaction are all in one place.

Shared sessions

The change with the clearest consequence is shared cloud sessions. More than one person can now take part in the same agent session while the context is preserved between them. Everything else in the release is described more broadly: the project lists improvements across messaging, memory, skills, models, automations, security, plugins, and the native apps, without giving details for each.

OpenClaw remains model-independent. It runs against hosted models, API providers, or local models, and the project keeps state management self-hosted.

The upgrade did not go smoothly for everyone. InfoQ reports mixed community reception, with some users upgrading without trouble while others hit migration problems, broken gateways, lost automations, or model authentication failures. Full release notes are published under the project's docs at version 2026.8.1.

Shared sessions are the part worth paying attention to, because they change what kind of tool this is. A single-operator agent produces work that has to be described to everyone else afterwards. A session two people can be inside means the handoff carries the context with it: someone picks up a half-finished task and sees what the agent was told, what it tried, and where it stopped.

The setup change matters less on its own but removes a real adoption cost. Teams that already pay for model access do not have to set up separate keys just to try the thing, which is usually the step where an evaluation is delayed for a week waiting on someone with billing access.

Against that, the migration reports are a reason to pin your current version and test the upgrade on a test setup you can throw away first. A release that merged half the project's lifetime pull requests in seven weeks is a large amount of code to change at once, and broken automations are exactly the failure that shows up days later rather than during the upgrade.

Source

Primary source: OpenClaw, 30 August 2026. Coverage: InfoQ, 1 September 2026.