OpenClaw ships on an aggressive cadence -- roughly one tagged release every few days through April 2026. If you are running stable channel, you are already on v2026.4.21 (tagged April 22). If you prefer living closer to the edge, beta and dev channels are also available via openclaw update --channel <name>.
Below is a consolidated snapshot of what has landed recently, what broke, and what the core team is actively fixing.
This is the release you should be running. According to the PatchBot changelog and the detailed breakdown on OpenClaw Playbook, the headline changes are:
The bundled OpenAI image-generation provider now defaults to gpt-image-2, and tool metadata advertises newer 2K/4K size hints. If you generate blog headers, mockups, or social assets through the built-in image lane, this is a direct quality upgrade -- no config changes required.
Critically, when automatic provider fallback kicks in, failed candidates are now logged at warn level before the system moves on. Previously a later provider could succeed while silently hiding the original failure. If you are debugging flaky image generation, this alone justifies the upgrade.
A new bundled plugin called Skill Workshop captures reusable workflow corrections as pending or auto-applied workspace skills. It runs threshold-based reviewer passes to prioritize completion bias on reusable procedures, quarantines unsafe proposals, and refreshes skill metadata. Think of it as the agent learning from its own mistakes -- within a governed envelope.
Owner-enforced commands now require real owner identity when enforceOwnerForCommands=true, instead of letting wildcard allowFrom behavior or an empty owner-candidate list silently grant permission. This is exactly the kind of boundary fix that prevents privilege escalation through permissive fallback paths.
PR #70501 (merged April 23) adds Azure OpenAI endpoint support for image generation. Previously, pointing openai.baseUrl at an Azure deployment broke image generation entirely because the image provider was never taught Azure-style auth headers (api-key instead of Authorization: Bearer), deployment-scoped URLs, or the required api-version query parameter. The chat completions path already handled all of this; the image path was simply lagging behind. The companion docs update (commit bc01cbb) covers endpoint usage.
| Area | Change |
|---|---|
| Plugins/doctor | Bundled plugin dependency recovery from openclaw doctor paths repaired |
| Slack | Runtime sends now preserve thread aliases when threadTs is provided |
| Browser | Invalid ax<N> accessibility refs rejected immediately instead of timing out |
| npm | node-domexception alias mirrored into root overrides, reducing install noise |
| Thinking/reasoning | Implicit reasoning models now default to medium instead of an ambiguous resolution path (commit 87eee6e) |
As summarized on the OpenClaw Facebook community and the PatchBot entry:
"API key" placeholder was added to provider key prompts (#69553)./think -- the reasoning command now adapts based on which provider/model is running, saving tokens and producing better results per model.| Version | Key Changes |
|---|---|
| v2026.4.15 | Anthropic defaults to Claude Opus 4.7; Gemini TTS support added to the google plugin (#67515) |
| v2026.4.14 | Forward-compat for gpt-5.4-pro (#66453); explicit turn improvements for GPT-5 family; core refactors for performance |
| v2026.4.12 | Active Memory plugin -- dedicated memory sub-agent that auto-pulls relevant context before replies; Convex-backed Telegram credential leasing (#65596) |
| v2026.4.11 | ChatGPT import ingestion in Dreaming (#64505); webchat structured chat bubbles with [embed ...] tag (#64104) |
A notable community observation from r/openclaw: a user posted "Is v.2026.4.11 the first version in a while that did not break things?" -- reflecting the tension between rapid iteration cadence and stability that the project has been navigating since the 3.x line.
The most recent push activity is dominated by Peter Steinberger aggressively trimming and stabilizing the test suite:
| Commit | Scope |
|---|---|
0839617 | Drop obsolete Docker fs bridge smoke test |
c1ba7f7 | Remove Docker from fs bridge smoke |
4dcd6b8 | Slim gateway live connect smoke |
1bbca1d | Move full Docker checks to daily CI schedule |
d3dc890 | Fix: Allow installed plugins through allowlist |
87eee6e | Fix: Default implicit reasoning models to medium (by Tak Hoffman, #70601) |
bc01cbb | Docs: Azure OpenAI endpoint usage for image generation (by Otto Deng, #70501) |
03477cc | Fix: Add runner label to /status output (#70595) |
e6d1ce9 | Fix: Update WeCom blurb (by Sliverp, #70614) |
The pattern here is clear: the team is paying down CI reliability debt by extracting Docker-dependent tests into a daily schedule rather than running them on every push, while shipping targeted fixes in parallel.
Several high-impact issues remain open. If you are hitting any of these, check the linked issues for workarounds and subscribe for updates.
The single most reported issue this week. Multiple users on fresh Ubuntu 24.04 installs hit Error: Cannot find module '@larksuiteoapi/node-sdk' during the setup wizard when the Feishu extension is loaded.
The closed duplicates suggest a partial fix landed (likely the plugin allowlist commit d3dc890), but #70587 confirms the crash still reproduces on a clean install as of today. If you hit this, the practical workaround is to run openclaw doctor after install and ensure optional extensions (Feishu, Nostr) are not loaded unless you explicitly need them.
Issue #70623 reports two distinct channel regressions in 2026.4.21:
"Agent couldn't generate a response" even on successful turns.openclaw doctor reports OK, but no sessions are created. The channel is effectively a black hole.Issue #70622 documents a scenario where a real tool failure (e.g., an exec command returning an auth/permission error) causes the assistant to enter repeated error=terminated responses instead of producing a normal failure explanation. The tool result lands correctly in session history, but the post-tool assistant reply gets stuck in a termination loop. This is related to the broader family of interrupted-streaming-tool-call issues tracked in #53109.
Issue #67710 notes that anthropic/claude-opus-4-7 is accepted by the config system but resolves as default,configured,missing in openclaw models list. Despite v2026.4.15 defaulting Anthropic selections to Opus 4.7, the model catalog resolver has not caught up for all entry points. Setting it as default can break your setup silently. The recommended workaround is to pin to anthropic/claude-opus-4-6 until the resolver is updated.
Issue #70620 reports out-of-order and missing messages between the AI assistant and the WeChat client via the openclaw-weixin plugin. Investigation messages sent by the agent (e.g., "checking session logs") are not visible on the WeChat side, while the AI interface shows a completely different conversation narrative. This points to a buffering or queue ordering problem in the WeChat plugin.
Issue #70619 is a meticulous diagnosis of stale lifecycle fields (status, startedAt, endedAt) leaking from prior runs into fresh isolated cron sessions. The per-run :run:<sessionId> row inherits metadata from the previous execution, producing run rows marked done while the current run is still active. This joins a family of related cron state-inheritance bugs (#66380, #62707, #11506).
| Issue | Resolution |
|---|---|
#38728 — Feishu TTS audio file_type=opus | Closed April 23. Feishu requires file_type=opus for audio messages; the plugin was uploading as mp3. |
| #70198 — Missing extension deps (Windows) | Closed April 23. Plugin allowlist fix. |
#70292 — Missing @larksuiteoapi/node-sdk (Ubuntu) | Closed April 23. Same allowlist fix, though #70587 suggests it may not cover all install paths. |
| #70487 — Azure OpenAI image gen broken | Closed April 23. Azure endpoint auth, URL, and api-version support added to the image provider. |
#70195 — Subagent spawning pairing required (1008) | Closed April 23. Pairing scope-upgrade regression for sessions_spawn addressed. |
| #70177 — Telegram DM amnesia via claude-cli | Closed April 23. cliSessionBindings persisting phantom session IDs that had no backing transcript file. |
If you are coming from v2026.4.20 or earlier:
gpt-image-2 default and 2K/4K size hints should produce noticeably sharper output with no config changes.claude-opus-4-6 if you rely on the Opus alias. The 4.7 model ID is not yet fully resolved in the catalog (#67710).openclaw doctor after install. If you hit the @larksuiteoapi/node-sdk crash (#70587), ensure Feishu is not auto-loaded unless you need it.sessionTarget: "isolated", verify that run rows show correct lifecycle fields -- the stale-inheritance bug (#70619) may produce misleading status until a fix lands.OpenClaw's release cadence is genuinely unusual for a project of its scale -- roughly seven tagged releases in two weeks of April. The upside is that fixes and features land fast. The downside, which the issue tracker makes painfully visible, is that some releases introduce regressions that get patched in the next cycle. The missing-extension-dependency crash, for instance, was reported, closed, and then reported again within 48 hours on a different install path.
The structural trend, though, is positive. The team is paying down CI and test debt in real time (witness today's ~10 commits dedicated to slimming smoke tests and parallelizing Docker checks). Security boundaries are being tightened with each release. And feature depth -- Active Memory, Skill Workshop, Azure provider parity -- continues to expand.
For developers building on OpenClaw as a platform, the practical advice is straightforward: pin your version, test before upgrading, and keep openclaw doctor in your deploy checklist. The lobster moves fast. Make sure your nets are ready.