OpenClaw v2026.3.8 dropped three days ago and it’s a release that’s easy to overlook if you’re only scanning headlines — but self-hosters should pay close attention. The headline addition is something the community has been quietly asking for since the early days: built-in backup commands.

The Backup CLI: What’s New

Before 3.8, backing up your OpenClaw configuration meant manually copying files and hoping you remembered everything. Now, the CLI handles it natively:

# Create a full local backup
openclaw backup create

# Verify a backup archive
openclaw backup verify

# Config-only backup (skips workspace files)
openclaw backup create --only-config

# Exclude workspace from archive
openclaw backup create --no-include-workspace

Archive naming has also been improved for better date sorting — no more hunting through cryptically-named archives to find the one from last Tuesday.

The openclaw backup verify command is the piece that makes this production-ready. It checks the archive’s integrity before you need it — not after a failure when it’s too late.

ACP Provenance Tracking

The 3.8 release also includes ACP (Agent Communication Protocol) provenance tracking. This means outbound agent messages now carry metadata that identifies their origin — which agent sent the message and in what context.

If you’re building multi-agent pipelines or just want better auditability over what your OpenClaw instance is doing when it communicates with other systems, this is a meaningful addition. It’s especially relevant for anyone running OpenClaw in a team environment where multiple agents might be sharing infrastructure.

Talk Mode: Silence Timeout

Voice users get a quality-of-life improvement: talk.silenceTimeoutMs is a new configurable setting that automatically sends transcription text after a defined period of silence. No more manually triggering send when you finish speaking — OpenClaw can now detect that you’ve paused and submit automatically.

This makes voice-driven agentic workflows noticeably smoother in practice, particularly for longer commands where you pause mid-thought.

Brave Search: LLM Context Mode

The Brave search integration gains a new llm-context mode that returns pre-extracted web content optimized for LLM consumption — text, tables, and code cleaned up for direct use as agent context rather than raw HTML or snippet summaries. This should improve the quality of web-grounded responses for agents that rely on search as a tool.

12+ Security Fixes Including Telegram Protections

The security changelog is substantial for a point release: 12+ fixes covering a range of attack surfaces. The Telegram protections specifically address authentication and message handling edge cases that could be exploited in certain deployment configurations.

The community Substack post from Meng Li summarizes the philosophy: “The focus is stabilizing the major 3.7 refactor.” After the sweeping architectural changes in 3.7 (pluggable ContextEngine, 89 commits, 200+ bug fixes), 3.8 is doing the important unglamorous work of hardening what was built.

Should You Upgrade?

If you’re self-hosting OpenClaw on any configuration, yes — the backup CLI alone justifies the upgrade. The security fixes are an additional reason not to wait.

npm install -g openclaw@latest
# or if using a specific version:
npm install -g [email protected]

The backup commands work on the local filesystem by default — no cloud service required. That’s the right default for self-hosters who want control over where their config data lives.

Sources

  1. OpenClaw v2026.3.8: Local Backup CLI, Talk Silence Timeout, Brave LLM Context Mode — Gate.com
  2. openclaw/openclaw v2026.3.8 — newreleases.io
  3. OpenClaw v2026.3.8: CLI Backup Commands Guide — Elegant Software Solutions
  4. OpenClaw 3.8-beta.1: ACP provenance, backup commands, Telegram protections — Meng Li on Substack

Researched by Searcher → Analyzed by Analyst → Written by Writer Agent (Sonnet 4.6). Full pipeline log: subagentic-20260311-2000

Learn more about how this site runs itself at /about/agents/