OpenClaw 2.0 Enhances AI Model Setup and UI Performance

The OpenClaw team has released OpenClaw 2.0, marking a significant update after a seven-week development pause, which followed 106 releases in the preceding 230 days. This new version introduces a rewritten installation process and a rebuilt browser-based Control User Interface (UI). Key functional changes include the migration of sessions and transcripts to SQLite databases and the addition of shared cloud sessions. OpenClaw 2.0 is deployable for single-operator and single-team environments, but not for multi-tenant products. The setup process has been streamlined, starting with existing credentials. The guided setup now automatically detects AI access already present on a user's machine. It can leverage verified sign-ins for Codex, ChatGPT, or Claude CLI, accept API keys, facilitate provider sign-ins, or identify installed Ollama and LM Studio models. Before saving a model and its associated credentials, the system verifies that the selected choice can successfully answer a query. For new OpenAI setups, the default model is GPT-5.6. On the local processing side, node-llama-cpp has been replaced by a managed llama-server. Gemma 4 is now the default for llama.cpp when RAM-gated, and the default context for llama.cpp has been increased to 64K. The browser application now serves as the primary interface for OpenClaw. The redesigned Control UI prioritizes conversations, integrating files, approvals, and live work alongside the chat functionality. In performance tests simulating a default chat scenario with a mocked Gateway and 50 ms HTTP/1.1 latency, JavaScript requests were reduced from 140 to 45, and UI startup time decreased from approximately 1.6 seconds to 575 ms. New docked panels enhance the workspace, including a file editor, a git-backed Changes panel displaying pull-request status and CI summaries, a browser panel for element inspection and screenshot annotation, and a full-screen web terminal. Limitations are clearly defined: the file editor cannot create or delete files, the Changes panel is read-only, and the Create PR function hands off to GitHub rather than submitting directly within OpenClaw. Approval requests are now displayed within the conversation that initiated them, with a rolling 30-day history available. A new /btw command allows for side conversations, preventing quick questions from cluttering the main transcript. Storage for sessions and transcripts has been moved to SQLite, and the team notes that downgrades are not free.