OpenClaw Adds Restart Recovery and a 30-Day Usage View in New Release

OpenClaw’s new release gives users a 30-day view of usage and adds recovery for unfinished work after a restart. Version 2026.9.6 also puts public GitHub discussions and code changes beside chat.

A longer view of agent work

The web interface shows usage across the full session report a user can access. The 30-day view is therefore bounded by that user’s access; it is not a promise of one report covering every session in an organization.

Someone can also start a separate background task from the command palette using text or a pasted screenshot, without replacing the current chat and draft. If task creation fails, the palette keeps the images for another try. Closing it normally discards unsent images.

When setup stalls

On Windows, the installer can try other Node package-manager options after one fails, then download an official portable runtime into the user’s account. That fallback needs no administrator access, but setup still stops if it cannot validate a supported runtime.

Other failures get more specific guidance. Invalid configuration points users to an explicit repair command. If Podman lacks a required helper, OpenClaw explains the repair without installing it or disabling existing sandbox protections. On FreeBSD, an unsupported source installation stops before changing the existing installation and directs users to a package route.

2,614Pull requests

OpenClaw lists 2,614 pull requests in the version 2026.9.6 release notes.

178Direct commits

The release notes count 178 direct commits.

350Contributors

OpenClaw credits 350 contributors.

More project context inside chat

The new GitHub reader brings public discussions and diffs—the changes between versions of code—alongside a conversation. Remote workspaces gain Files, Memory and Skills. OpenClaw also adds chat-model support for Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7.

A new custom agent created in a local workspace now saves its approved purpose as instructions for later conversations. Existing instructions remain intact; a conflict requires another workspace, and changing the proposed purpose requires fresh approval. The feature cannot be combined with bundled-role templates or remote workspaces.

Starting elsewhere without losing your place

For new cloud conversations, the placement picker makes the operating system, machine size and starting branch easier to confirm. Prompts and attachments stay visible during startup, and opening the created conversation does not send the prompt again. The picker does not resize existing instances.

If a user leaves the starting branch for a new worktree untouched, OpenClaw uses the fetched remote default branch. A saved or explicitly chosen local branch keeps its meaning. If Git discovery fails, the system preserves a saved separate-worktree choice rather than silently switching to the current checkout; starting waits for recovery or an explicit switch.