Memory (Memoria)
Use this skill when OpenClaw should treat Memoria as the durable external memory system for the current user or project.
Routing
Pick the smallest reference that matches the task:
- - Install or verify the OpenClaw plugin: INLINECODE0
- Decide which memory tool to use: INLINECODE1
- Daily store, recall, correct, forget behavior: INLINECODE2
- Session lifecycle, goals, recovery, branches, rollback: INLINECODE3
Core Rules
- 1. Prefer Memoria tools over
MEMORY.md or memory/YYYY-MM-DD.md unless the user explicitly asks for file-based notes. - Do not auto-store every turn. Save durable facts, preferences, decisions, workflows, and meaningful progress.
- On task resume or "what do you remember" prompts, retrieve relevant memory first.
- Use the most specific tool available:
memory_profile for stable preferences, memory_store for general durable memory, memory_correct or memory_forget for repairs. - Before bulk delete, purge, or large rewrites, create a snapshot first.
- Use branches for risky or reversible memory experiments, then diff and merge or delete.
- After important writes, repairs, rollback, or merges, verify with retrieval or list tools.
- Do not claim only
memory_search or memory_get exist when other memory_* tools are available.
Default Flow
- 1. At conversation start or task resume, use
memory_retrieve or memory_search for relevant context. - During the conversation, store only the durable facts worth keeping.
- If the user corrects or removes memory, repair it immediately with
memory_correct, memory_forget, or memory_purge. - For risky memory maintenance, create a snapshot or branch before mutating state.
- At the end of meaningful work, store the durable outcome and clean up obsolete working memory.
Important Notes
- - OpenClaw's built-in file memory is separate from Memoria.
- The Memoria plugin defaults to explicit writes, not silent auto-capture.
- INLINECODE18 is a compatibility helper; when in doubt, prefer
memory_retrieve, memory_search, or memory_list. - Memoria's core strengths are semantic retrieval, durable cross-session memory, snapshots, rollback, branches, merge, and governance.
Quick Start
CODEBLOCK0
记忆(Memoria)
当OpenClaw需要将Memoria视为当前用户或项目的持久化外部记忆系统时,使用此技能。
路由指引
选择与任务匹配的最小参考文档:
- - 安装或验证OpenClaw插件:references/setup.md
- 决定使用哪个记忆工具:references/tool-surface.md
- 日常存储、回忆、修正、遗忘行为:references/operations.md
- 会话生命周期、目标、恢复、分支、回滚:references/patterns.md
核心规则
- 1. 优先使用Memoria工具,而非MEMORY.md或memory/YYYY-MM-DD.md,除非用户明确要求使用基于文件的笔记。
- 不要自动存储每一轮对话。仅保存持久化的事实、偏好、决策、工作流程和有意义的进展。
- 在任务恢复或收到你记得什么的提示时,首先检索相关记忆。
- 使用最具体的可用工具:memoryprofile用于稳定偏好,memorystore用于通用持久化记忆,memorycorrect或memoryforget用于修正。
- 在执行批量删除、清除或大规模重写之前,先创建快照。
- 对于有风险或可逆的记忆实验,使用分支,然后进行差异比较、合并或删除。
- 在重要写入、修正、回滚或合并之后,使用检索或列表工具进行验证。
- 当其他memory*工具可用时,不要声称只有memorysearch或memory_get存在。
默认流程
- 1. 在对话开始或任务恢复时,使用memoryretrieve或memorysearch获取相关上下文。
- 在对话过程中,仅存储值得保留的持久化事实。
- 如果用户修正或删除记忆,立即使用memorycorrect、memoryforget或memory_purge进行修复。
- 对于有风险的记忆维护操作,在变更状态前创建快照或分支。
- 在有意义的工作结束时,存储持久化结果并清理过期的临时记忆。
重要说明
- - OpenClaw内置的文件记忆与Memoria是分开的。
- Memoria插件默认采用显式写入,而非静默自动捕获。
- memoryget是兼容性辅助工具;如有疑问,优先使用memoryretrieve、memorysearch或memorylist。
- Memoria的核心优势在于语义检索、持久化跨会话记忆、快照、回滚、分支、合并和治理。
快速开始
bash
openclaw plugins install @matrixorigin/memory-memoria
openclaw plugins enable memory-memoria
openclaw memoria install
openclaw memoria verify