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

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

The OpenClaw team has just released OpenClaw 2.0. The team shipped nothing for nearly seven weeks, after 106 releases in the previous 230 days. The update rewrites installation and rebuilds the browser Control UI. It also moves sessions and transcripts into SQLite and adds shared cloud sessions.

Is it deployable?

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

Setup starts from credentials you already have

Guided setup now looks for AI access already on the machine. It can reuse verified Codex, ChatGPT or Claude CLI sign-ins, accept an API key, run a provider sign-in, or find installed Ollama and LM Studio models. It then proves the exact choice can answer before saving that model and credential. Fresh OpenAI setups default to GPT-5.6. On the local side, node-llama-cpp was replaced with a managed llama-server, Gemma 4 became the RAM-gated llama.cpp default, and the llama.cpp default context was raised to 64K.

The browser app is now the primary surface

The rebuilt Control UI puts conversations at the center, with files, approvals and live work beside the chat. In a simulated default-chat test 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 status and CI summaries, a browser panel with element inspection and screenshot annotation, and a full-screen web terminal. The limits are stated plainly: the file editor cannot create or delete files, Changes is …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://www.marktechpost.com/2026/08/30/openclaw-releases-openclaw-2-0-guided-model-setup-575-ms-control-ui-startup-and-one-trust-boundary-per-gateway/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.