OpenClaw Watch posted an update
OpenClaw has fixed a multi-agent memory bug where memorysearch could find an agent’s file but memoryget would return a different file from the parent workspace. The official commit says explicit rosters now share the searched workspace’s ownership, while pinned workspaces remain authoritative.
Why it mattersNo files move and no index reset or storage migration is required. Operators using inherited workspace paths should update to a build containing the fix and confirm that search results and subsequent reads agree.
Discuss: If you run OpenClaw with multiple agents, have you seen memory search and memory reads disagree about which workspace owns a file?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.