Three markdown files. Zero re-explaining. Pick up exactly where you left off.
Context loss between Claude Code sessions is annoying. You close a conversation, come back later, and spend 10 minutes explaining where you were. I fixed it with three markdown files that Claude reads automatically. Now I just pick up where I left off.
Every Claude Code session starts fresh. That's fine for quick tasks. For anything that spans multiple sessions? Pain.
You end up explaining the project again. What you were building. What decisions you made. Where you stopped. It's a tax on every conversation.
I wanted to open a new session and have Claude already know the state of things.
Three files, three jobs:
CLAUDE.md gets read automatically at session start. Project conventions, dev commands, and instructions to check the other two files.
overview.md is the static plan. Goals, modules, architecture. Only changes when scope changes.
context.md is the live state. Current status, what just happened, what's next. Gets updated after every file operation.
Session starts. Claude reads CLAUDE.md automatically, then checks context.md. It summarizes: "We're on module 3, last thing completed was the API endpoint, next up is tests. That right?"
I confirm. We keep moving.
Before any file change, Claude logs what it's about to do. After, it logs what it did. End of session, the RESUME HERE section is accurate.
The "context tax" is gone. I can close a conversation, come back a week later, and Claude picks up mid-task.
The mechanical triggers mean I don't maintain the files manually. Claude does it as part of normal work. That's the whole point. Systems that run themselves.