Memory + ModelsPersistent Memory
Persistent Memory
Persistent memory for familiar identity, user preferences, project conventions, and long-term operating rules.
1 min read
Persistent memory is for stable facts that should survive context resets and daemon restarts. It is the layer that gives a familiar continuity.
Good persistent memories
- Familiar identity and role.
- User preferences and communication style.
- Project conventions and hard rules.
- Stable infrastructure notes.
- Repeated lessons from prior incidents.
Poor persistent memories
- Raw command output.
- One-off failed hypotheses.
- Secrets, tokens, or private URLs.
- Temporary task state.
- Facts that are likely to expire quickly.
Promotion rule
Promote memory deliberately. A good persistent memory should still be useful weeks later and should not expose private material in the wrong context.
For concrete sessions and outcomes, use Episodic memory. For concept-based recall, use Semantic memory.
Was this page helpful?No
Last updated on