Persistent project memory for Kimi Code, based on opencode-mem's local vector storage. Exposes memory capabilities as MCP tools for semantic search, storage, and management of project decisions, bug fixes, and technical details.
kimi-mem provides 9 tools with consistent naming (memory_* prefix) and reasonable descriptions in Chinese. However, critical gaps undermine production readiness: (1) Parameter descriptions are minimal or absent for many fields (e.g., memory_search's 'scope' enum lacks explanation of project vs all-projects semantics); (2) Output schemas are completely undocumented, no tool declares what fields it returns, forcing LLMs to guess; (3) Error handling is absent, no guidance on recovery, retryability, or actionable error messages; (4) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (DESTRUCTIVE, WRITE); (5) Chinese descriptions limit accessibility for English-speaking agents and developers. Naming is consistent but generic (memory_* verbs are clear). Schemas are present in input but lack depth and output documentation.
立即保存一条长期记忆(重要决策、bug 根因、用户偏好等)。日常对话产生的记忆会自动捕获,无需手动调。
导出当前项目记忆为可移植 JSON 文件
删除一条记忆(按 id)
从 JSON 文件导入记忆到当前项目(默认会重新计算 embedding;存在相同 id 则中止)
列出最近保存的记忆
列出所有项目 shard(含孤儿 path 关联),用于发现项目迁移后的孤儿记忆
项目目录迁移后,把孤儿 shard 重新绑定到当前 cwd(先用 list_shards 查 fromPath/fromHash)
Output schemas completely undocumented. No tool declares return type, fields, or structure. LLMs cannot plan downstream calls or extract required data.
Parameter descriptions are minimal or missing. 'scope' enum in memory_search lacks explanation of project vs all-projects semantics. 'type' in memory_add lacks guidance on when to use each category.
No error handling guidance. Tools marked DESTRUCTIVE (memory_forget) and WRITE (memory_add, memory_import, memory_migrate) lack recovery hints, retryability classification, or actionable error messages.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
查看跨项目的用户工作偏好画像
语义搜索长期记忆(项目决策、bug 修复、技术细节)。工作开始前可主动搜一下相关上下文。
Tool annotations missing. Despite clear risk levels (DESTRUCTIVE, WRITE, READ_ONLY), no tools declare readOnlyHint, destructiveHint, or idempotentHint. Agents cannot infer safety properties.
Descriptions in Chinese limit accessibility. English-speaking agents and developers cannot understand tool purpose, parameters, or constraints without translation.