Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(claude): refresh ai-memory routing block (scopes/global/read-page)
Djalma Júnior9d69968ec823
diff --git a/CLAUDE.md b/CLAUDE.mdindex bf10d93f..6f6a0d5c 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -308,7 +308,7 @@ match the intent to the tool. They do not need to name the tool.| User says / situation | Tool ||---|---|-| "have we discussed X?" / "search memory for Y" / before proposing architecture | `memory_query` |+| "have we discussed X?" / "search memory for Y" / before proposing architecture | `memory_query` (current project; `scopes` for named siblings; `global=true` to search every project) || "what's been going on" / "show recent activity" (light) | `memory_recent` || "is ai-memory healthy?" / "how big is the wiki?" | `memory_status` || "give me the stats" / structured snapshot for the agent to consume | `memory_briefing` |@@ -318,6 +318,7 @@ match the intent to the tool. They do not need to name the tool.| "save context for the next session" / wrapping up | `memory_handoff_begin` (single-use handoff; terse summary; put detail in `open_questions` + `next_steps` bullets) || "consolidate this session" / "compile what we learned" (also runs on PreCompact; at session end only if `AI_MEMORY_CONSOLIDATE_ON_SESSION_END` is set) | `memory_consolidate` || "remember this permanently" / "save a note" / "add an annotation" / durable project knowledge | `memory_write_page` (write a wiki page; do **not** use handoff for permanent notes) |+| "read the page about X" / "show me the full content of Y" / "open the page on Z" | `memory_read_page` (full body; pass a query to search or `path` for a direct lookup) || "audit the wiki" / "find contradictions" / "what rules should we add?" | `memory_lint` || "prune old pages" / "memory cleanup" | `memory_forget_sweep` |@@ -326,6 +327,26 @@ going on" use case — it returns a prose digest whose verbosityscales automatically to how long it's been since the last activity(< 1 h → one line; > 30 days → full catchup).+### When the current project comes up empty — broaden the search++`memory_query` searches only the **current** project by default. If a+search comes back empty or thin, the knowledge may live in a **sibling+project** — shared `infra`, `ops`, or a related app. Broaden instead of+concluding "we never recorded it":++- **Know which projects to check?** Re-run with explicit `scopes`, e.g.+ `scopes: [{ "workspace": "default", "project": "infra" }]`.+- **Don't know where it lives?** Pass `global=true` to search **every**+ project in every workspace at once; each hit is annotated with its+ workspace + project. `global=true` cannot be combined with+ `scopes`/`project`/`workspace`.++`memory_query` returns **snippets, not full page bodies** — an empty or+short snippet does **not** mean the page is empty (a large page can+match outside the snippet window). To read the whole page, use+`memory_read_page` (by `path`, or pass a `query` to fetch the top hit's+full body).+### When you write a project rule, write it hereIf you're about to write a durable project rule ("always X", "never