OpenClaw 2026.3.8 Adds Backups, Better macOS Setup, and Smarter Web Search Tools
OpenClaw 2026.3.8 is out, and while this is not the kind of release that completely reinvents the platform, it does add a surprising number of practical upgrades for people who actually rely on OpenClaw every day.
The update focuses on a mix of backup tools, macOS onboarding improvements, new browser and web search options, better ACP provenance handling, and a long list of bug fixes across messaging, browser control, gateway recovery, and platform integrations. In other words, this is the kind of release that makes OpenClaw easier to trust in real-world use, not just easier to demo.
Backup tools are one of the biggest additions
One of the most useful changes in OpenClaw 2026.3.8 is the addition of new CLI backup commands. The platform now supports openclaw backup create and openclaw backup verify, which gives users a more direct way to protect local state and validate archives before something goes wrong.
That matters because OpenClaw setups are increasingly becoming long-lived working environments rather than throwaway test installs. The new backup flow also includes options like config-only backups, workspace exclusion, and archive verification, which should make it easier for users to recover cleanly after mistakes, failed upgrades, or machine migrations.
macOS users get a better onboarding experience
Apple users also get some meaningful quality-of-life upgrades in this release. OpenClaw 2026.3.8 adds a remote gateway token field for remote mode in the macOS onboarding flow, preserves existing non-plaintext token values unless they are explicitly replaced, and warns users when the loaded token format is not usable directly inside the macOS app.
That may sound minor on paper, but it points to a bigger theme in this release. OpenClaw is doing more work to reduce setup friction without silently breaking security-sensitive configuration along the way.
Talk Mode and TUI both get smarter
Another useful addition is a new top-level talk.silenceTimeoutMs config setting. This lets users control how long Talk Mode waits after silence before automatically sending the current transcript.
That is the kind of feature that sounds small until it becomes part of a daily workflow. For people using OpenClaw in voice-heavy setups, especially on mobile or desktop mic workflows, being able to tune that pause window could make interactions feel noticeably smoother.
The TUI also gets a practical improvement here. OpenClaw can now infer the active agent from the current workspace when launched inside a configured agent workspace, while still respecting explicit session targets when they are already set.
Web search gets more flexible
OpenClaw 2026.3.8 also expands its Brave web search support with a new optional llm-context mode. When enabled, the web_search tool can call Brave’s LLM Context endpoint and return extracted grounding snippets with source metadata.
That is a genuinely useful step forward. Search results are one thing. Search results packaged in a way that is easier for agents to reason over are much more valuable, especially for research-heavy workflows.
The release also cleans up provider ordering and related web search documentation, which should make setup less confusing for users juggling multiple providers or legacy configuration.
ACP provenance is now more visible
One of the more interesting additions in this release is optional ACP ingress provenance metadata and receipt injection through the openclaw acp --provenance flag.
That gives OpenClaw a better way to preserve and report ACP-origin context with session trace IDs. For people using ACP-based workflows heavily, that kind of traceability is not just nice to have. It can make debugging and handoff visibility much easier.
The fix list is long, and that is probably the point
As usual, the fix section tells the bigger story.
OpenClaw 2026.3.8 includes recovery fixes for macOS launchd restarts, browser relay improvements, Telegram DM deduping, cron announce reliability, Android distribution changes, better config snapshot handling, browser CDP fixes, gateway timeout recovery, and a wide range of security hardening updates.
Some of the more notable fixes include:
| Area | What changed | Why it matters |
|---|---|---|
| Gateway restart recovery | Restart-triggered shutdowns now fail loud when they time out instead of looking like clean stops | That should make supervised restarts more reliable. |
| Browser relay | Relay now waits briefly for previously attached Chrome tabs to reappear after transient drops | That should reduce flaky tab reconnect failures. |
| Telegram DMs | Inbound DM dedupe logic was tightened | Users should see fewer duplicate replies in edge cases. |
| Config/runtime snapshots | Resolved secret-backed config snapshots are now preserved better after writes | That helps avoid confusing follow-up reads after config changes. |
| Security hardening | Additional SSRF, plugin route, command approval, and archive extraction protections landed | This release continues OpenClaw’s push toward safer defaults. |
OpenClaw 2026.3.8 key changes at a glance
| Feature | What OpenClaw 2026.3.8 adds |
|---|---|
| Backup tools | New create and verify commands for local state archives |
| macOS onboarding | Remote gateway token handling improvements and safer token preservation |
| Talk Mode | Configurable silence timeout before auto-send |
| TUI | Workspace-based active agent inference |
| Web search | Optional Brave LLM Context support with grounding snippets |
| ACP | Optional provenance metadata and receipt injection |
| Version output | Short git commit hash can now appear in openclaw --version |
Final take
OpenClaw 2026.3.8 feels like a practical release. It does not hang everything on one flashy feature, but it does improve backup handling, onboarding, web search flexibility, provenance tracking, and system reliability in ways that should matter to serious users.
That is probably the right move for OpenClaw right now. The platform is already broad. The bigger challenge is making that breadth easier to manage, easier to recover, and easier to trust. This update looks like a solid step in that direction.