Independent OpenClaw reporting, releases, guides, and community coverage
Guides

OpenClaw 2026.9.1 Ships Chat Diagrams

OpenClaw 2026.9.1 adds Mermaid diagrams, faster setup, safer updates, shared skill libraries, and broader mobile polish.

Filed under Guides 4 min read Updated Sep 6, 2026
OpenClaw 2026.9.1 Ships Chat Diagrams

OpenClaw 2026.9.1 is now the latest stable release, published on September 3 with a wide set of upgrades across chat rendering, first-run setup, Gateway recovery, approvals, Android, providers, and package artifacts.

The release is larger than a routine patch. It bundles visible user-facing improvements, several operator reliability fixes, and a verified npm publication under the 2026.9.1 version. The GitHub release also includes dependency evidence, a release manifest, post-publish evidence, Windows companion installers for x64 and arm64, and SHA256 sums.

Diagrams Land In Chat

The most visible change is native Mermaid rendering. Mermaid blocks now render as diagrams inside the Control UI and the native macOS, iOS, and Android apps. The release notes also call out enlarge previews and a retry path when mobile diagram rendering fails.

That matters because OpenClaw conversations often contain plans, workflows, dependency graphs, and architecture sketches. Previously, users could paste Mermaid and still need a separate viewer to inspect the result. With 2026.9.1, diagram output becomes part of the normal chat surface.

For teams using OpenClaw as an operational agent, this is not just a cosmetic change. It makes runbooks, architecture explanations, and incident timelines easier to inspect inside the same conversation where the agent generated them.

Setup Gets Shorter

Fresh installs also get a faster path from package install to usable chat. The release notes say new installs, including npx openclaw@latest, now offer a quick-start lane that detects existing Claude Code or Codex logins and API keys, verifies them live, and opens the web dashboard from a foreground Gateway.

The full custom setup remains available, but the default experience should feel less like a wizard and more like an immediate handoff into a working OpenClaw session.

This is one of the release's clearest adoption improvements. A smoother first run reduces the gap between "I installed it" and "I have an agent running with my existing model access."

Safer Updates And Gateway Recovery

OpenClaw 2026.9.1 puts a lot of weight behind upgrade and Gateway reliability. The release notes describe update rollback when post-update Doctor fails, preservation of config and secret references across failed upgrades, plugin readiness checks before restarts, and a built-in triage agent for failed updates.

Gateway startup also gets harder to break. The release says startup now recovers under load and with large agent rosters, quarantines malformed legacy cron rows instead of blocking boot, degrades on migration warnings rather than refusing to start, and keeps Windows Gateways online after an agent restart.

For self-hosted users, those changes hit the boring but essential part of OpenClaw: the agent should come back after an update, a migration, a big roster, or a rough restart. A failed upgrade that preserves state and gives actionable recovery is much better than a silent broken service.

Skills, Approvals, And Mobile Polish

The release also expands personal skill libraries on shared Gateways. Users can keep personal skills beside the workspace set, import ZIP archives, and share or publish libraries per identity on team Gateways.

Codex approvals now stick more consistently too. The release highlights durable "Allow Always" behavior for MCP tools on OpenClaw-configured servers, session-aware tool approval posture, and approval reuse for active Codex placements.

Android continues to close the gap with the web Control UI. The release notes mention matching chat, sidebar navigation, and appearance settings, a composer that grows to six lines, and recording support when dictation is unavailable.

What To Watch

OpenClaw 2026.9.1 is a broad release, but a few themes stand out:

  • Chat is becoming a richer working surface, not just a transcript
  • Fresh installs are being optimized for users who already have model accounts
  • Updates and Gateway recovery are getting more durable
  • Shared Gateways are becoming more personal through skill libraries
  • Mobile clients are catching up with Control UI behavior

The npm registry now reports 2026.9.1 as both latest and beta, with extended-stable still on 2026.6.34. For users tracking stable OpenClaw, this is the new release to evaluate.


Release v2026.9.1 · published September 3, 2026 · source: OpenClaw GitHub

Daily Briefing

Get the Open-Source Briefing

The stories that matter, delivered to your inbox every morning. Free, no spam, unsubscribe anytime.

Join 45,000+ developers. No spam. Unsubscribe anytime.