OpenClaw Release Roundup: What Actually Changed in March 2026?

OpenClaw moved fast in March 2026. If you only saw the star count and the hype, it would be easy to miss that the product itself was also changing quickly underneath operators. Messaging channels got better. Approvals got sharper. Coding workflows improved. Detached work became more structured. Search and provider integrations got more serious.

This roundup is the practical version of the changelog: not every line item, just the changes that actually altered how OpenClaw behaves.

Why Was March 2026 Such a Big Month for OpenClaw?

Because the releases did not all point in the same direction. Some were user-facing polish releases. Others were trust-boundary releases. Others were infrastructure releases. Together, they made OpenClaw feel much more like a platform and less like a rapidly growing experiment.

The clean way to think about the month is:

• 3.24 improved channels and API compatibility.
• 3.28 sharpened provider setup and approvals.
• 3.31 made background tasks a real system.
• 4.1 exposed that task system more clearly and added search and guardrail upgrades.

What Shipped in 3.24?

Version 3.24 was where OpenClaw clearly strengthened its messaging and client surfaces. The biggest changes were native Microsoft Teams via the official SDK, Slack interactive reply buttons, Discord auto-thread naming, and broader OpenAI-compatible API coverage with /v1/models and /v1/embeddings.

That release mattered if you cared about channel quality, Teams deployments, or using OpenClaw behind OpenAI-compatible clients like OpenWebUI. It also improved the skills management UI enough that the Control UI started feeling more operator-friendly instead of purely developer-oriented.

Read the full breakdown in our 3.24 update guide.

What Shipped in 3.28?

Version 3.28 was a more technical release. The big operator takeaways were the Qwen migration to Model Studio API keys, first-class x_search for xAI, plugin approval hooks, and default apply_patch support for OpenAI and Codex models.

This was the release where approvals started to move closer to the real tool boundary, and where coding workflows got materially better for OpenAI/Codex users. It was also the point where OpenClaw signaled that very old config would not be auto-massaged forever.

That makes 3.28 especially relevant for people who self-host, use multiple providers, or build heavier agent workflows rather than simple chat automations.

What Shipped in 3.31?

Version 3.31 was arguably the most operationally important release in the run. Detached work stopped feeling like a collection of special cases and started becoming a shared background-run control plane with a SQLite-backed ledger and task flows.

It also added QQ Bot, native Codex web search for embedded Pi runs, safer install-time behavior, and tighter auth and node-command defaults. That combination matters because it affects what OpenClaw can do, where it can run, and how safely it behaves when you automate more aggressively.

If 3.24 made the front-end surfaces stronger, 3.31 made the back-end operator model stronger.

What Landed in 4.1 Right After March?

Even though 4.1 published on April 1, it belongs in this same mental bundle because it extends the 3.31 task work. The new /tasks board surfaces background work directly in chat, the bundled SearXNG provider improves self-hosted search, and Bedrock Guardrails make AWS-heavy deployments more serious.

In other words: 3.31 built more of the task system, and 4.1 made it easier to see and use.

Which Updates Matter Most for Different Operators?

If you run Teams, Slack, or Discord heavily: prioritize 3.24.

If you use Qwen, Grok, or Codex-like coding flows: prioritize 3.28.

If you run long jobs, subagents, cron work, or detached execution: prioritize 3.31 and 4.1.

If you need Bedrock policy controls or self-hosted search: prioritize 4.1.

The bigger lesson is that OpenClaw is moving fast enough that “latest version” is not a cosmetic concept. Architecture, trust boundaries, and workflow ergonomics really are changing from release to release. If you want to stay current without reading every changelog line, keep this post, the 3.31 guide, and the 4.1 guide in your regular update routine.