store_memory
Store structured codebase memories—patterns, conventions, decisions—to persist across sessions using SQLite.
Instructions
Store a structured memory for the current project. Use this when you discover important codebase patterns, conventions, decisions, or architecture details that should persist across sessions. Memories are stored in SQLite and survive restarts.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| namespace | No | Memory group (default: "codebase"). Use "codebase" for coding memories. | codebase |
| memoryType | Yes | Memory kind: "map" (file tree, architecture), "convention" (coding rules, patterns), "decision" (technical choices + rationale), "snapshot" (current focus/blockers, use with ttlHours), "dependency" (key packages), "error_pattern" (recurring fixes) | |
| key | Yes | Unique identifier within namespace+type (e.g., "file-tree", "naming-convention", "chose-sqlite-over-postgres") | |
| value | Yes | The memory content — structured JSON preferred (e.g., {"pattern": "camelCase", "scope": "variables"}) | |
| priority | No | Injection priority 1-10 (10 = always inject, 5 = default, 1 = low priority) | |
| confidence | No | Confidence 0.0-1.0 (1.0 = certain, lower = inferred) | |
| ttlHours | No | Auto-expire after N hours (use for snapshots/focus, omit for permanent memories) | |
| projectId | No | Project ID (defaults to current project) |