| name | remember |
| description | Explicitly save an insight, decision, or learning to mempalace long-term storage |
| argument-hint | [what to remember] |
| user-invocable | true |
The user wants to save this to long-term memory: $ARGUMENTS
Quick start
Call memory_save with content, concepts, and files.
Why
Preserve knowledge across sessions so it can be retrieved later via recall.
Workflow
- Analyze the user's input: extract the core insight, decision, or fact.
- Extract 2-5 searchable
concepts (lowercased keyword phrases, specific over generic).
- Extract relevant
files (absolute or repo-relative paths).
- Call
memory_save with content, concepts, files.
- Confirm to the user with the concepts you tagged.
Anti-patterns
WRONG -- generic concepts that won't match future searches:
{"concepts": ["auth", "code", "bug"]}
RIGHT -- specific, searchable concepts:
{"concepts": ["jwt-refresh-rotation", "token-expiry-handler"]}
WRONG -- editing the user's phrasing in content:
// Paraphrasing changes the meaning. Preserve the user's exact words.
RIGHT -- preserving original phrasing:
{"content": "We decided to use XDG_CONFIG_HOME as the primary config directory..."}
MCP tool unavailable
If memory_save is not available:
- Run
/plugin list in Claude Code, confirm mempalace is enabled.
- Restart Claude Code (
.mcp.json is only read on startup).
- Check
/mcp to see if the mempalace MCP server is connected.
See _shared/TROUBLESHOOTING.md and EXAMPLES.md for more.