OpenClaw shipped 2026.8.2 today, a stable release that turns a wide set of recent fixes into a packaged update for desktop, browser, mobile, channel, cloud, voice, and plugin users. The release was published at 16:00 UTC on September 1, 2026, with npm, Docker, Linux, Android, Windows, ClawHub, and plugin publication proof attached to the release notes.
The headline is not just one feature. OpenClaw 2026.8.2 is a reliability release with several user-facing improvements: a Linux desktop companion, dockable Home, background-session launch from New Session, safer update recovery, stronger reply completion, and more dependable voice delivery.
What Is New
The release brings Home closer to active work. Users can open Home in a right or bottom dock with Cmd/Ctrl+Shift+H, keep the current page visible, preview or remove its work-context snapshot, and attach selected text before sending a message.
Linux users also get a desktop companion path. The release notes say x86-64 Linux users can install a .deb package or AppImage, connect to a local or remote Gateway, and open Quick Chat from the system tray or an X11 keyboard shortcut. AppImage updates are signature-verified, while .deb packages remain under the package manager.
Background sessions also become easier to start. New Session can now create and run work in the background without switching pages, while preserving the selected local, cloud, or paired-device placement. Completion notices can open the finished session.
Safer Upgrades
OpenClaw 2026.8.2 puts a lot of attention into update and repair behavior. The release notes call out preservation of newer configuration, clearer failure when session migration blocks startup, and recovery of a stopped Gateway after a failed update when the installed package or rollback is verified safe.
Operators also get cleanup tooling. openclaw update cleanup --dry-run can preview retained migration originals before explicit removal. The release notes are careful about the tradeoff: cleanup preserves current SQLite history but permanently gives up rollback to removed originals.
That emphasis matters because OpenClaw runs as a long-lived local system for many users. Upgrade code has to protect configuration, state, plugin capability review, service setup, and rollback paths at the same time.
Reply And Voice Reliability
The release includes several fixes aimed at making conversations finish cleanly. Settled tool work should now be followed by a visible final answer, and failed accepted turns should surface a failure instead of leaving a conversation at tool output or an initial acknowledgement.
Voice also gets a large bundle of repairs. The release notes mention keeping internal reasoning out of speech, preserving tool-generated audio through delivery, and keeping later browser Talk turns working after call setup. Transcription, speech providers, voice settings, and browser Talk all receive focused fixes.
For channel users, 2026.8.2 covers iMessage, Telegram, LINE, Discord, Slack Enterprise approvals, Google Chat formatting, and other delivery paths. The common theme is ownership: keep the right conversation, account, channel, and authorization attached to the work that produced the message.
Verification And Known Limits
The release includes unusually detailed publication proof. The npm package is published as 2026.8.2, with latest pointing to that version while the newer beta tag is preserved. The release notes include registry tarball integrity, a signed release tag, full-release validation links, plugin publication details, Docker manifest digests, and ClawHub verification records.
There are still known issues. The notes say standalone @openclaw/memory-lancedb installs can still resolve an older vulnerable Sharp version through an optional Transformers dependency, though the reviewed text-embedding and vector-storage path does not load that image adapter. Hindi and Korean token labels also have wording reversed for used and total counts, while the counts themselves are unchanged.
Operator Takeaway
OpenClaw 2026.8.2 is the stable release to watch if you use Linux, Home, voice, browser relay, background sessions, or managed updates. It packages a large backlog of reliability work into a verified stable train and gives operators clearer proof about exactly what was published.