memorix_store
Store and index observations like code decisions, bug fixes, and insights across projects. Classify by type, track progress, and persist memories locally to share knowledge across multiple IDEs.
Instructions
Store a new observation/memory. Automatically indexed for search. Use type to classify: gotcha (🔴 critical pitfall), decision (🟤 architecture choice), problem-solution (🟡 bug fix), how-it-works (🔵 explanation), what-changed (🟢 change), discovery (🟣 insight), why-it-exists (🟠 rationale), trade-off (⚖️ compromise), session-request (🎯 original goal). Stored memories persist across sessions and are shared with other IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, Trae) via the same local data directory.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entityName | Yes | The entity this observation belongs to (e.g., "auth-module", "port-config") | |
| type | Yes | Observation type for classification | |
| title | Yes | Short descriptive title (~5-10 words) | |
| narrative | Yes | Full description of the observation | |
| facts | No | Structured facts (e.g., "Default timeout: 60s") | |
| filesModified | No | Files involved | |
| concepts | No | Related concepts/keywords | |
| topicKey | No | Optional topic identifier for upserts (e.g., "architecture/auth-model"). If an observation with the same topicKey already exists in this project, it will be UPDATED instead of creating a new one. Use memorix_suggest_topic_key to generate a stable key. Good for evolving decisions, architecture docs, etc. | |
| progress | No | Progress tracking for task/feature observations |