|

OpenClaw Releases OpenClaw 2.0: Guided Model Setup, 575 ms Control UI Startup, and One Trust Boundary Per Gateway

ByRicardo

The OpenClaw crew has simply launched OpenClaw 2.0. The crew shipped nothing for almost seven weeks, after 106 releases within the earlier 230 days. The replace rewrites set up and rebuilds the browser Control UI. It additionally strikes periods and transcripts into SQLite and provides shared cloud sessions.

Is it deployable?

Yes for single-operator and single-team deployments. No for multi-tenant merchandise.

Setup begins from credentials you have already got

Guided setup now appears to be like for AI entry already on the machine. It can reuse verified Codex, ChatGPT or Claude CLI sign-ins, settle for an API key, run a supplier sign-in, or discover put in Ollama and LM Studio fashions. It then proves the precise alternative can reply earlier than saving that mannequin and credential. Fresh OpenAI setups default to GPT-5.6. On the native facet, node-llama-cpp was changed with a managed llama-server, Gemma 4 turned the RAM-gated llama.cpp default, and the llama.cpp default context was raised to 64K.

The browser app is now the first floor

The rebuilt Control UI places conversations on the heart, with recordsdata, approvals and dwell work beside the chat. In a simulated default-chat take a look at with a mocked Gateway and 50 ms HTTP/1.1 latency, JavaScript requests fell from 140 to 45 and startup fell from roughly 1.6 seconds to 575 ms.

Docked panels add a workspace file editor, a git-backed Changes panel with pull-request standing and CI summaries, a browser panel with aspect inspection and screenshot annotation, and a full-screen net terminal. The limits are said plainly: the file editor can’t create or delete recordsdata, Changes is read-only, and Create PR arms off to GitHub reasonably than submitting inside OpenClaw. Approval requests seem contained in the dialog that triggered them, with a rolling 30-day historical past. A /btw command opens a facet dialog so a fast query doesn’t pollute the primary transcript.

Storage moved to SQLite, and downgrades are usually not free

Sessions and transcripts now dwell in SQLite. Before rolling again to an older file-backed launch, the present CLI should restore archived legacy transcript artifacts, and periods created after the migration won’t seem in older releases. Take a verified backup earlier than upgrading.

Multiplayer, with an specific ceiling

Shared cloud sessions let a second particular person be part of dwell work or take it over with context intact. Owners and directors select whether or not somebody could learn, counsel adjustments, work in a draft, or take part immediately. The documentation is direct in regards to the ceiling: these controls are usually not tenant isolation and not a safety boundary. Incognito is off by default, retains its dialog in course of reminiscence, and nonetheless sends messages to the mannequin supplier.

Security posture to evaluate earlier than rollout

The Gateway binds to loopback by default, and most chat channels reply an unknown DM sender with a pairing code. openclaw safety audit checks inbound entry, instrument blast radius, community publicity, browser management publicity and plugin allowlists.

Model alternative is handled as the primary mitigation for immediate injection. OpenClaw cites a 2026 crowdsourced enviornment of 272K assaults throughout 41 agent eventualities, scored solely when the agent each executed the dangerous motion and hid it from the person: 0.5% success in opposition to Claude Opus 4.5, 1.0% in opposition to Sonnet 4.5, 1.3% in opposition to Haiku 4.5, and 8.5% in opposition to Gemini 2.5 Pro. The similar web page warns that adaptive human attackers nonetheless exceed 80% success in opposition to state-of-the-art defenses, so instrument coverage, exec approvals and sandboxing stay the arduous enforcement layer.

Interactive explainer

Key Takeaways

  • v2026.8.1 lands 16,000+ PRs from 933 contributors, about half of OpenClaw's complete merge historical past.
  • Guided setup reuses current subscriptions, API keys and native fashions, and verifies the mannequin earlier than saving.
  • Rebuilt Control UI reduce test-harness startup from ~1.6 s to 575 ms and JS requests from 140 to 45.
  • Shared cloud periods add actual multiplayer, however the docs say they don't seem to be a safety boundary.

Check out the release notes and OpenClaw 2.0 Technical details. Also, be happy to comply with us on Twitter and don’t overlook to hitch our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to accomplice with us for selling your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar and so forth.? Connect with us

The publish OpenClaw Releases OpenClaw 2.0: Guided Model Setup, 575 ms Control UI Startup, and One Trust Boundary Per Gateway appeared first on MarkTechPost.

Similar Posts