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
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| claude-code | ✓ | Auto memory saves Claude's accumulated notes to ~/.claude/projects/<project>/memory/MEMORY.md; requires CC v2.1.59+; enabled by default |
| 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 .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 |