Skip to contentllms.txt

auto_memory

Whether the provider auto-generates persistent rules from conversation context. Distinct from user-authored rules — these are AI-created and stored separately.

Type: bool Content type: rules

ProviderSupportedMechanism
claude-code✓Auto memory saves Claude's accumulated notes to ~/.claude/projects/<project>/memory/MEMORY.md; first 200 lines or 25KB loaded at session start; requires CC v2.1.59+; enabled by default; disable via CLAUDE_CODE_DISABLE_AUTO_MEMORY=1; override storage location via autoMemoryDirectory setting (accepted from policy/user settings and --settings flag, not from project or local settings); subagents can also maintain their own auto memory
gemini-cli✓memory_command: Gemini CLI /memory command saves notes that persist across sessions as rule-like content
windsurf✓auto_generated_memories: Windsurf AI generates persistent memories stored in ~/.codeium/windsurf/memories/ as rule-like files
amp✗Amp does not have an AI-generated auto-memory system
cline✗Cline does not have an AI-generated auto-memory system distinct from user-authored rules
codex✗Codex does not have an AI-generated auto-memory system
copilot-cli✗Copilot CLI does not have an AI-generated persistent memory system for rules
crush✗No runtime memory/append command documented for Crush rule files
cursor✗Cursor does not document an AI-generated auto-memory system distinct from user-authored rules.
factory-droid✗Factory Droid does not have an AI-generated auto-memory system
kiro✗Kiro does not have an AI-generated auto-memory system separate from user-authored steering files
opencode✗No runtime command documented for persisting notes into rule files
pi✗Pi does not have an AI-generated auto-memory system
roo-code✗No auto-append or persistent memory command documented for rule content
zed✗Zed does not document a command that persists agent memory into the rules file