Release

OpenClaw shipped v2026.3.22 today, and it’s the biggest release the platform has seen in months. If you’ve been waiting for a native plugin ecosystem, longer-running agents, or GPT-5.4 access, this is the update you’ve been waiting for. Here’s what’s new — and what breaks. The Headline Feature: ClawHub Plugin Marketplace OpenClaw now has a native plugin marketplace called ClawHub. When you run openclaw plugins install <package>, it checks ClawHub first, falling back to npm only when ClawHub doesn’t have that package or version. ...

OpenClaw shipped version 2026.3.22 today, and the release notes read like the team decided to clear out a year’s worth of backlog in one shot. There’s a native plugin marketplace, a long-overdue timeout fix, expanded model support, a substantial security patch batch, and the final closure of the MoltBot rebrand saga. This one has breaking changes — read carefully before you update. The Headliner: ClawHub Plugin Marketplace The biggest architectural addition in this release is ClawHub — a native plugin marketplace baked directly into the OpenClaw runtime. Previously, extending OpenClaw meant hunting down npm packages or manually managing skill directories. ClawHub centralizes this: you can now browse, install, and update skills and plugins from a curated registry without leaving the tool. ...

For most of OpenClaw’s history, backing up your configuration meant manually copying files, writing shell scripts, or hoping your dotfiles repo was up to date. With v2026.3.8, that changes: OpenClaw now ships with built-in backup CLI tools that make protecting your setup first-class behavior, not an afterthought. This guide covers the new openclaw backup commands, how to use config-only mode, how to verify your backups, and how to restore if things go wrong. ...

OpenClaw shipped v2026.3.13 early this morning, and it’s a meaningful release for anyone running browser automation, using OpenClaw on mobile, or hitting dashboard performance walls on heavy agentic runs. The headline feature is the Chrome DevTools Protocol (CDP) attach mode — a native integration that lets OpenClaw connect directly to a signed-in live Chrome session for real-time debugging and automation. That’s a significant capability addition: instead of spinning up an isolated browser profile, you can now attach to the Chrome instance you’re already using, complete with your active sessions, cookies, and extensions. ...

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: ...

OpenClaw version 2026.3.8 is out, and it’s a substantive release. More than two dozen fixes land across all platforms, with the headline features addressing three pain points that have frustrated OpenClaw users since at least the previous major version: missing local backup tooling, unreliable gateway restarts on macOS, and fragile API key exposure in logs. New: Local Backup CLI The biggest new feature is the backup command pair: openclaw backup create openclaw backup verify backup create produces a local snapshot of your agent state, configuration, and critical data. backup verify checks the integrity of an existing backup without restoring it — useful for scheduled validation in production setups. ...

The OpenClaw project shipped its biggest release of 2026 this morning: v2026.3.7, built by 196 contributors and packed with features that fundamentally extend what agents can do with memory, context, and model choice. If you run OpenClaw in production, stop what you’re doing — there’s a breaking change you need to handle before restarting. The Headline Feature: ContextEngine Plugin Slot This is the one that changes architecture discussions. OpenClaw now exposes a first-class ContextEngine plugin slot with a full lifecycle hook API: ...

OpenClaw just shipped v2026.3.2 — and it’s one of the more substantial point releases in recent memory. With a built-in PDF analysis tool, a new Speech-to-Text API, expanded credential management, and over 150 bug fixes, this update touches nearly every corner of the platform. There are also breaking changes to the HTTP Route Registration API that existing users need to know about before upgrading. Here’s what’s in the box. PDF Analysis Tool: Documents as First-Class Inputs The headline feature of v2026.3.2 is native PDF analysis. OpenClaw agents can now ingest PDF documents directly, with support for both Anthropic and Google backends. That dual-backend architecture matters: you can route PDF parsing to whichever model handles your document type best — Anthropic’s Claude for dense text and reasoning-heavy documents, Google’s multimodal stack for PDFs with heavy visual content like charts, diagrams, and scanned pages. ...

OpenClaw 2026.3.1 is out, and it’s a meaningful update — not just a bug-fix release. Three headline features define this version: OpenAI WebSocket streaming, Claude 4.6 adaptive reasoning integration, and a new suite of code review workflow tools. If you’re running OpenClaw as a development partner or agentic pipeline backbone, this one’s worth your attention. OpenAI WebSocket Streaming: Faster, More Responsive Agent Replies Previous versions of OpenClaw used standard HTTP request/response for OpenAI model calls, which meant you’d wait for the full generation to complete before seeing any output. 2026.3.1 changes that by implementing WebSocket-based streaming for OpenAI models — the same pattern that makes ChatGPT’s web interface feel fast and interactive. ...

If you run Claude Code in production, v2.1.63 is not a routine patch. This release ships a meaningful architectural shift — HTTP hooks — alongside two genuinely useful slash commands and a pile of memory leak fixes that explain why long-running Claude Code sessions sometimes go sideways. The Big One: HTTP Hooks Replace Shell-Based Hooks Previous versions of Claude Code let you hook into the agent lifecycle via shell commands. It worked, but it was clunky: you were spawning subprocesses, dealing with shell escaping, and losing type safety the moment data crossed the boundary. ...