project-memory

You can persist context across Claude Code sessions by using external memory files like docs/status.md and docs/decisions/*.md to capture project status, decisions, and technical debt for continuity between runs.

Tracking technical debt and decisions across coding sessions is best handled by maintaining dedicated memory files like docs/tech-debt.md and docs/decisions/*.md, ensuring centralized documentation that supports handoffs and audits.

To start a session with previous context, you should review docs/status.md, check the git state, and read recent decision logs to establish the current project baseline before coding.

Yes, the session management system integrates with git workflows by checking git state during the start protocol and using a commit-history workflow to track actions and context changes across sessions.

Yes, you can use external memory files structured as docs/decisions/*.md to log decisions for long-running development projects, providing centralized documentation that ensures cross-session continuity and audit readiness.

Using markdown files for cross-session memory requires manual adherence to start and end session protocols to capture context accurately, meaning context may be lost if sessions end unexpectedly without saving status updates.