OpenClaw Ships v2026.3.13-1 Recovery Patch with Compaction Checks and Discord Fixes
What Happened
The OpenClaw team shipped version 2026.3.13-1 on March 16 as a recovery release to address a broken Git tag in the original v2026.3.13 build. Beyond the tag fix, the release introduces several meaningful improvements: compaction sanity checks that use full-session token counts to prevent data corruption during long-running agent sessions, improved handling of Discord gateway metadata fetch failures, and session state preservation for lastAccountId and lastThreadId across agent resets.
On the client side, the Android app's chat settings received a UI redesign with grouped device and media configuration sections. Browser automation capabilities were enhanced with batched action execution and more reliable CSS selector targeting — improvements that directly benefit users relying on OpenClaw for web scraping and form-filling workflows.
Why It Matters
The rapid patch cadence — three releases in three days (v2026.3.12 on March 13, v2026.3.13 on March 14, and v2026.3.13-1 on March 16) — highlights both the project's remarkable development velocity and the stability challenges that come with it. The compaction sanity checks are particularly notable: as agent sessions grow longer and accumulate more context, data integrity during memory compaction becomes critical. Without proper safeguards, agents can lose context mid-task or produce inconsistent behavior after session resets.
What's Next
The broken-tag incident that necessitated the -1 recovery release points to a need for more robust CI/CD and release validation processes — something the project will likely formalize as it matures under OpenAI stewardship. Users running production workloads should update to v2026.3.13-1 immediately, as it also includes security patches from the v2026.3.13 beta cycle, including fixes for exec approval handling and Ollama reasoning visibility that prevented internal chain-of-thought from leaking into user-facing replies.