remember ยท diff

git:20260713.d4415d7 to git:20260714.1f13344

10 added, 3 removed. Audit A to A.

---
name: remember
description: Save an explicit user-requested memory with memtomem. Use only when the user clearly asks to remember, record, or persist information for later.
argument-hint: [content to remember]
- allowed-tools: mcp__plugin_memtomem_memtomem__mem_add, mcp__memtomem__mem_add
+ allowed-tools: mcp__plugin_memtomem_memtomem__mem_add, mcp__memtomem__mem_add, mcp__plugin_memtomem_memtomem__mem_status, mcp__memtomem__mem_status
disable-model-invocation: true
---
# Remember information
Use `$ARGUMENTS` as the content to remember.
If the request does not clearly specify the content to remember, ask before calling a tool.
- Confirm that the user explicitly requested persistence, then call `mem_add` with the requested content. Add a natural title and a small set of useful tags only when they are clear from the content.
+ Confirm that the user explicitly requested persistence. Add a natural title and a small set of useful tags only when they are clear from the content.
- Use `scope="user"` by default and leave `force_unsafe=false`. Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`. Report the written file and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant.
+ Choose the destination from the user's context:
+
+ - For a project-specific fact or decision, call `mem_status` first. If the current project has a registered `.memtomem/memories.local` source, call `mem_add` with `scope="project_local"`.
+ - If the request is project-specific but that tier is not registered, do not silently fall back to user memory. Ask the user to run `cd <project-root> && mm mem init --scope project_local`, then retry.
+ - Use `scope="user"` only for cross-project preferences or when the user explicitly requests personal/global memory.
+ - Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`.
+
+ Always leave `force_unsafe=false`. Report the effective scope, written file, and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant.