session-memory

Session memory persists context by storing logs, decisions, and learned patterns under .claude/memory/context.json, enabling you to recall previous sessions and reuse patterns across ongoing projects.

Tracking decisions and learned patterns is managed through session memory, which saves context and traces to context.json with local and global separation to maintain a single source of truth.

Yes, session memory supports both manual and automated logging policies, allowing you to control how context, decisions, and traces are saved to the memory directory during your workflow.

Local and global separation in session memory organizes context logs by scope, ensuring project-specific traces remain isolated while broader learned patterns stay accessible across different sessions.

You need session memory persistence when working on multiple sessions within the same project, requiring you to recall previous context, track historical decisions, and reuse learned patterns to maintain continuity.

No, session memory operates without external dependencies, storing all context, decisions, and traces directly within the local .claude/memory/ directory structure for immediate access.