From 452a1b63418715adc43492b5fab4b7f95049e138 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-agent[bot]" Date: Thu, 23 Apr 2026 22:08:58 +0000 Subject: [PATCH] docs: refresh documentation --- docs/concepts/memory-qmd.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/concepts/memory-qmd.md b/docs/concepts/memory-qmd.md index 6047e1ec029..96d5c665fbe 100644 --- a/docs/concepts/memory-qmd.md +++ b/docs/concepts/memory-qmd.md @@ -43,6 +43,9 @@ OpenClaw creates a self-contained QMD home under automatically -- collections, updates, and embedding runs are handled for you. It prefers current QMD collection and MCP query shapes, but still falls back to legacy `--mask` collection flags and older MCP tool names when needed. +Boot-time reconciliation also recreates stale managed collections back to their +canonical patterns when an older QMD collection with the same name is still +present. ## How the sidecar works @@ -166,6 +169,11 @@ Set to `120000` for slower hardware. **Empty results in group chats?** Check `memory.qmd.scope` -- the default only allows direct and channel sessions. +**Root memory search suddenly got too broad?** Restart the gateway or wait for +the next startup reconciliation. OpenClaw recreates stale managed collections +back to canonical `MEMORY.md` and `memory/` patterns when it detects a same-name +conflict. + **Workspace-visible temp repos causing `ENAMETOOLONG` or broken indexing?** QMD traversal currently follows the underlying QMD scanner behavior rather than OpenClaw's builtin symlink rules. Keep temporary monorepo checkouts under