Evidence record / openclaw

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-openclaw-memory-saving-turns-retain-their-persistence-only-tool-boundary

Memory-saving turns retain their persistence-only tool boundary. Hidden pre-compaction memory-saving turns could regain execution or MCP tools after selecting a memory-only surface, allowing unrelated project work while a user’s request waited. 10.1 keeps the persistence restriction through host-tool collection, client/MCP assembly and final harness presentation. File-backed saves keep read and the append-only daily-memory writer; provider-backed saves keep read and the selected plugin’s declared persistence/lookup tools. Normal foreground tooling remains available.

Channel: tagged-release, retained at 10.3. Half: defect. Date: 2026-10-10 first stable 2026.10.1.

Operator consequence: Include this fixed assembly path when depending on background memory work staying within its role. A memory-saving label alone was not an enforcement boundary. The fix requires no configuration or state migration and is included in the 10.3 stable pin.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-openclaw-memory-saving-turns-retain-their-persistence-only-tool-boundary

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact