save_memory
Record facts, preferences, decisions, and architecture details to persist across all Claude Code sessions for future reference.
Instructions
Store a developer memory (fact, preference, decision, architecture detail). Memories persist across all Claude Code sessions and are available in future conversations.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The fact to remember (complete sentence) | |
| memory_type | No | Type: identity, preference, architecture, decision, bug, dependency, pattern, context. Custom types also accepted for non-developer domains. | context |
| category | No | Category: frontend, backend, database, devops, testing, security, performance, tooling, api, general. Custom categories also accepted for non-developer domains. | general |
| subject | No | What this is about, e.g. "auth_system", "react_version", "tab_width" | |
| importance | No | 1-10 (10 = core architecture, 1 = trivial) | |
| scope | No | global = applies everywhere, project = specific to this codebase, team = shared with team members | project |
| team_id | No | Team ID (required when scope is "team"). The memory will be shared with all team members. | |
| tags | No | Optional tags for grouping/threading memories (max 5 tags, each max 30 chars). E.g., ["marketing-campaign", "feb-2026"] | |
| ttl | No | Set an expiration time. Use for temporary context like current task status. Format: "24h", "7d", "30d". Memory auto-archives after expiry. | |
| project_id | No | Project identifier override (auto-detected from CLAUDE_PROJECT_DIR or git remote if omitted) |