OpenClaw 2.0 expands from personal agent runtime into a persistent multi-machine workspace

OpenClaw has released version 2.0, shipped as v2026.8.1, after an unusually long release cycle for the open-source agent project. The scale is substantial: the official release record lists 16,962 unique pull requests in the release range, while the project says 933 contributors participated. More important than the raw count is the scope. Installation, the browser experience, sessions, automations, plugins, model routing, native surfaces and security controls all changed in the same release.\n\nThe clearest product shift is toward persistent work that can move beyond the machine running the main Gateway. Sessions can now execute on paired devices or cloud workers while the Gateway remains the owner of the conversation and durable state. OpenClaw also adds conversation search, durable progress cards, richer dashboards and shared-session workflows, making the browser interface closer to an operating surface for ongoing agent work than a simple chat front end.\n\nAutomation and credential handling also receive material changes. Version 2.0 can request credentials through masked prompts without placing their values in chat or model context, and recurring automations can be granted narrowly scoped permissions that remain inspectable and revocable. Plugin installation surfaces more capability and security information before changes are accepted. These controls matter for OpenClaw because its usefulness comes from letting agents touch files, accounts, tools and remote execution environments; stronger controls reduce risk but do not remove the need for careful deployment and authentication.\n\nThis is not a frictionless upgrade. The bundled OpenProse plugin and /prose command are removed, shipped codex/* and openai-codex/* routes migrate to openai/*, and the release notes identify additional plugin-SDK migration gates beginning September 1. Existing users should therefore treat 2.0 as a migration event: back up state and configuration, read the breaking-change notes, run the project’s doctor/fix tooling where appropriate, and verify plugins and automation routes before assuming an old deployment will behave identically.\n\nFor AiToolMap, this is a material product update rather than a routine release note. OpenClaw’s review needs revalidation because the update changes the core product surface around persistence, distributed execution, collaboration, permissions and security. The existing review remains the current public snapshot until that revalidation passes the full evidence and integrity gate.