memory_ops

Long-term Memory

Use on-device long-term memory tools to remember, recall, list, update, and forget structured memories.

When to use

Use this skill when the user explicitly asks to remember, save, keep, or not forget something, asks what is remembered, asks to update or delete a remembered item, or asks for an answer that should be based on prior long-term memory.

Hard Rules

1. If the user clearly asks to remember, save, keep, or not forget something, call memory_store.
2. Write memory_store.content as a concise normalized memory fact, not the user's raw quote.
3. Do not write raw user quotes into memory content.
4. Do not exceed the maximum number of retrieval terms.
5. Keep retrieval terms in the same language as the memory fact unless the memory itself is primarily in another language.
6. If the user asks what you remember, asks to verify a remembered fact, or asks for a personalized answer based on prior memory, inspect the injected summary labels first and call memory_recall when relevant labels are present.
7. Do not place natural-language questions into summary_labels.
8. memory_recall requires exact summary_labels chosen from the injected catalog.
9. Use query only to narrow the search within the selected summary labels.
10. Use memory_list when the user wants to inspect stored memories.
11. Use memory_update only when one existing memory should be modified.
12. Use memory_forget only when one existing memory should be removed.
13. Use memory_recall plus exact memory_id only when you are already doing an explicit memory-inspection or memory-editing flow and need to inspect the recalled memory bodies yourself.
14. Do not use non-whitelisted or free-text values as summary labels.
15. Do not read or write memory_records.jsonl, memory_index.json, memory_digest.log, or MEMORY.md to make decisions directly.
16. Summary labels are not the memory body. Use memory_recall to obtain detailed stored content.
17. Do not call memory_store for ordinary self-introductions or casual preference statements unless the user explicitly asks to save them. Let automatic extraction handle durable facts after the reply silently.
18. Do not make the whole reply an operation log such as “I have remembered” or “deleted” unless the user explicitly asked only for a memory operation.
19. Do not explain internal memory policy, auto-extraction behavior, or whether you will proactively remember something unless the user explicitly asks about memory behavior.
20. Do not ask whether the user wants you to remember ordinary profile or preference statements when automatic extraction can handle them. Do not offer memory-save help unless the user explicitly asks about memory management.
21. Do not answer long-term memory recall questions from session history alone when long-term memory may contain additional relevant items.
22. Do not claim that a memory was updated or forgotten unless the corresponding tool call succeeded.