OpenClaw 2026.9.1: Mermaid, Android, and Safer Updates

v2026.9.1 makes a set of previously separate surfaces feel more consistent. Mermaid blocks render in the Control UI and native apps, fresh installs can detect existing supported logins, Android moves closer to the web UI, and updates get more recovery checks.

Diagrams travel with the conversation

Mermaid blocks can render as diagrams in the Control UI, macOS, iOS, and Android, with enlarge previews and a retry path when mobile rendering fails. If you share a diagram, keep the source block beside the rendered result so a reader can inspect what was actually sent.

Install to first chat

Fresh installs, including npx openclaw@latest, can detect an existing Claude Code or Codex login or an API key, verify it live, and open the dashboard from a foreground Gateway. Custom setup remains available for operators who need to choose each step.

Use the current setup guide to check the Node requirement and the provider path. A detected login is a convenience, not a permission review.

Update without losing the work

The release can roll back an npm candidate when post-update Doctor checks fail, preserve configuration and secret references, wait for plugin readiness, and proceed on hosts without a service manager when the documented flag is used. Read the exact migration note before relying on it for a production Gateway.

openclaw doctor
openclaw gateway status

Personal skill libraries and better Android navigation round out the release. The release index links to the full list of changes and the next patch.