Claude Code Forgets Everything Between Sessions. I Built a Fix.

Claude Code Starts From Scratch Every Session

If you use Claude Code every day, you've probably found yourself repeating the same explanations over and over again.

• Why did we choose this architecture?


• Why did we reject that implementation?


• What parts are we planning to improve later?

Even when you're working on the same project, Claude Code forgets everything once a session ends.

The conversation logs are still there—they're stored as JSONL files under ~/.claude/projects/—but Claude doesn't use them in future sessions. In other words, the memory exists, but the agent can't access it.

Git can tell you what changed, but it can't tell you why. The design decisions, trade-offs, and discussions that happened during development are often lost, even though they're some of the most valuable context for future work.

To solve this problem, I built an open source tool called memcp.