OpenClaw 2026.4.9 Update: Memory system overhauled and secured
• Current update overview
OpenClaw 2026.4.9 was released on 9 April.Rich.Significant upgrading of memory systems, multiple security loopholes, improvements to the Android/iOS platform, and 25+ problem restoration. Thanks to the participation of 15+ community contributors!
Memory system: Rem Backfill is here.
This is the top priority.Memory systemComprehensive upgrade:
- REM Backfill: can refill the historical memory and re-enter the old diary into Dreams and permanent memory without a second memory.
- Journal ViewAdd a structured journal view to support time-line navigation, backfill/replace control, retroactive dream summary
- Scene Lane.: Base scene channel with promotion tips to support phased back-filling
- Memory promotion: Short-term memory automatically promotes long-term memory
In short, your historical data will not be written in vain, so you can re-activate it as a useful long-term memory.
:: Safety repairs: 4 critical repairs
Several safety issues were repaired, including browsers, environmental variables, nodal execution, etc.:
1. Browser SSR security check enhancements
Reruns the blocked target security check to prevent the browser from bypassing the SSRF. The navigation that had previously been clicked, evaluated, and triggered by hooks may have bypassed the inspection and has now been repaired.
2. .env Document security
Stops running time control variables in untrusted workspace .env files, browser controls over and skips server environment variables, and rejects unsafe URL style browser controls over description.
3. Implementation of output purification at nodes
Marks remote node execution events (exec.starded, exec.finished, exec.denied) as untrusted system events, cleanses command/output/cause text provided by node and prevents remote node output from being injected into trusted system content.
4. Reliance on audit
Compulsively upgrade Basic-ftp to 5.2.1 in order to repair loopholes in CRLF commands and update Hono and @hono/node-server in production dependence.
• Platform improvements
Android pairs restore stability
- Could not close temporary folder: %s
- Direct operator and node sessions from new pairs
- Priority use of stored equipment after transfer Cards
- Pause automatic retry of pairs while applying backstage
Android pairs are now more reliable and can be restored with one scan.
iOS Version Fixed
The iOS release is now fixed to a clear CalVer (in apps/ios/version.json), keeping TestFlight in the same short version until the maintainer intends to upgrade the next gateway version.
Other important repairs
| Module | Fix Content |
|---|---|
| Matrix. | Waiting for synchronisation to be ready before the start is successful. Backstage processing program failed. |
| Slack | Keep the same source file.slack.com rearranger authentication, photo attachments back on load |
| Control UI | Prevents the reloading of old session history when fast session switching |
| Gateway/Chat | Contain ANNOUNCE SKIP/REPLY SKIP control token leaking to user interface |
| Auto-reply | Strip the sticky NO REPLY token to prevent the silent sentry text leaking |
| Sessions | Retain established external route to prevent delivery of external channel such as Telegram/Discord |
Provider improvements
- OpenAI: default missing observation effort is high, while supporting a visible run-time reasoning level
- Olama.: Allow the Ollama model using the original api: "ollama" path to display the reflection output when setting /think to a non-closed level
- Codex CLI: pass OpenClaw 's system tip to code interactions file configuration over
- Provider Auth: allow list of providers to declare providerAuth Aliases so that the provider variable can share environmental variables, authentication profile files, configuration support authentication and API key entry selection
Summary
OpenClaw 2026.4.9 is oneSecurity priorityThe version, which has repaired a number of potential security gaps, has also led to a significant upgrading of memory systems.
It is recommended that all users update as soon as possibleIn particular:
- User using browser function (SSRF repaired)
- Users using .env files (environmental variables secure)
- Users using Android pairs (stability restored)
- Users using the Matrix/Slack gateway (connect stability)
Update command:npm update -g openclaw
There is nothing wrong with security, and it is the way to be updated in a timely manner.
GitHub Publishing Page:https://github.com/openclaw/openclaw/releases