OpenClaw v2026.4.12-beta.1 Released — Safer plugin loading and more reliable memory recall
OpenClaw v2026.4.12-beta.1 narrows plugin activation to declared needs, improves memory recall defaults, and tightens self-update and provider documentation behavior.
OpenClaw v2026.4.12-beta.1 was published on 2026-04-12T23:27:07Z by steipete. OpenClaw v2026.4.12-beta.1 narrows plugin activation to declared needs, improves memory recall defaults, and tightens self-update and provider documentation behavior.
Quick answer
The standout change is startup discipline: fewer unrelated plugins loading at runtime, clearer trust boundaries, and better default behavior for memory-backed recall.
What's new in this release
- Plugins/loading: narrow CLI, provider, and channel activation to manifest-declared needs, preserve explicit scope and trust boundaries, and centralize manifest-owner policy so startup, command discovery, and runtime activation avoid loading unrelated plugin runtime. (#65120, #65259, #65298, #65429, #65459) Thanks @vincentkoc.
- Memory/active-memory: default QMD recall to search and surface better search-path telemetry so memory-backed recall works more predictably out of the box. (#65068) Thanks @Takhoffman.
- Docs/providers: expand bundled provider docs with richer capability, env-var, and setup guidance across provider pages.
- Docs/memory-wiki: add the recommended QMD + bridge-mode hybrid recipe plus zero-artifact troubleshooting guidance for `memory-wiki` bridge setups. (#63165) Thanks @sercada and @vincentkoc.
- CLI/update: respawn tracked plugin refresh from the updated entrypoint after package self-updates so `openclaw update` stops failing on stale hashed `dist/install.runtime-*.js` chunk imports. (#65471)
Why developers should care
Plugin-heavy deployments, provider maintainers, and teams debugging startup scope or memory recall quality are the core audience for this beta.
Upgrade notes
The fetched GitHub release notes mention breaking-change risk. Review the full release notes carefully before upgrading production agents, channels, or plugin-heavy environments.
Source
Full release notes: https://github.com/openclaw/openclaw/releases/tag/v2026.4.12-beta.1
Frequently asked questions
What changed in OpenClaw v2026.4.12-beta.1?
Plugins/loading: narrow CLI, provider, and channel activation to manifest-declared needs, preserve explicit scope and trust boundaries, and centralize manifest-owner policy so startup, command discovery, and runtime activation avoid loading unrelated plugin runtime. (#65120, #65259, #65298, #65429, #65459) Thanks @vincentkoc.; Memory/active-memory: default QMD recall to search and surface better search-path telemetry so memory-backed recall works more predictably out of the box. (#65068) Thanks @Takhoffman.; Docs/providers: expand bundled provider docs with richer capability, env-var, and setup guidance across provider pages.
Does OpenClaw v2026.4.12-beta.1 include breaking changes?
No explicit breaking changes were called out in the fetched GitHub release notes. Review the full release notes before upgrading provider-heavy, channel-heavy, or plugin-heavy environments: https://github.com/openclaw/openclaw/releases/tag/v2026.4.12-beta.1
Who should pay attention to OpenClaw v2026.4.12-beta.1?
Plugin-heavy deployments, provider maintainers, and teams debugging startup scope or memory recall quality are the core audience for this beta.