Every Claude Code session starts from scratch.
No memory of yesterday. No record of what you’re in the middle of. Whatever you were working on last time is gone - unless you bring it back yourself.
For a while, I dealt with this by front-loading context at the start of every session. A quick summary of what was active. Which projects mattered. Who I’d been talking to. What was still unresolved.
That worked until I started juggling more. Three client projects, internal work, a newsletter, an event with Adam. The “quick summary” got longer. I was spending the first few minutes of every conversation just getting Andy back up to speed.
The thing I really wanted: a system where Andy already knew what was active - without me having to tell it every time. Where small details mentioned in passing stayed accessible even after we’d moved on. Where context-switching didn’t mean starting over.
So I built it.
What the graph is
Andy keeps a weighted map of what I’m working on. Every topic that comes up in a conversation gets added to the map. The more I return to something, the more weight it builds. The less I touch it, the more it fades.
Nothing is pre-loaded. A topic enters the first time it surfaces - starting small, in the background. Work on it consistently and it moves toward the center. Stop working on it and it drifts toward the edge. Eventually it disappears.
No filing. No tags. No manual cleanup.
The map has three zones. Focus is what I’m actively working on - loaded automatically into every new conversation. Nearby is relevant but not front-and-center. Background is fading but not gone.
Domain renewal sat in Background for two weeks. Andy kept it.
The part that actually matters
Topics link to each other. When the client launch rose in priority, things connected to it - the domain renewal, the CMS work, the analytics setup - all got a small lift. Context travels with the work.
Different things decay at different rates. A person I’m working with holds their context and carries it into any project they’re connected to. A resolved technical detail fades faster. The system adapts to what tends to stay relevant.
I’m not maintaining any of this. It maintains itself based on what I keep coming back to.
Try it
I built an interactive demo that walks through a realistic week of context-switching - client work, internal projects, newsletter prep with Adam, then circling back. It starts with an empty canvas, because that’s where Andy actually starts. Topics appear when they come up. The moment where Andy surfaces an old note is in there.
The things mentioned once in passing are the hardest to hold. They’re also the most useful when you circle back to a thread three weeks later and need to know what was left unfinished.