Every conversation with Claude has a lifespan.
It starts fresh. A new Claude, a blank slate, no memory of who I am or how I work or what we’ve built together. I have to introduce myself. Explain the context. Re-establish the relationship. It’s like meeting someone at a party who’s heard of you but doesn’t really know you yet.
But then something shifts.
Somewhere in the middle of a long, productive session, Claude stops feeling like a new acquaintance and starts feeling like a colleague. It knows my shorthand. It anticipates my thinking. It pushes back in the right places and builds on my ideas in others. It gets me.
That’s the sweet spot. That’s what I’m chasing in every session.
And then — if I’m not paying attention — it starts to fade.
Claude begins to repeat a suggestion I already dismissed. It forgets something we established an hour ago. It presents a closed thread as if it’s new. The colleague feeling starts to slip, and something slightly generic takes its place.
That’s my signal. The context window is full. The session is ending whether I like it or not. (What a context window actually is, mechanically, is its own explanation — that’s Post 48, if you want the technical version. This post is just about what I do at the point it happens.)
What I do next matters enormously.
Why sessions need to be closed properly
A Claude session isn’t just a conversation. It’s a working relationship — and like any working relationship, it accumulates things that are worth keeping. Decisions made. Directions ruled out. Moments of real clarity. Stories that surfaced unexpectedly. The particular version of me that showed up that day.
If I just close the tab, all of that evaporates.
The next Claude I open will be a new puppy — enthusiastic, capable, but starting from scratch. It won’t know what we decided. It won’t know what I dismissed. It won’t know the story that came out of nowhere and turned out to be the most important thing in the session.
So I run a wrap-up. Every time.
There’s real research behind why this matters beyond just convenience. Writing something down does more than store it — the act of translating a thought into words is part of how the brain actually consolidates a short-term memory into a long-term one. And the benefit isn’t in the recording itself — research on reflective practice specifically finds that insight comes from examining an experience, not simply logging it. That’s the difference between a wrap-up and a transcript. A transcript just sits there. A wrap-up asks: what actually happened here, and what’s worth keeping?
What I capture
Three things. Always these three things.
The Real Sandi. How did I show up in this session? What did I say that surprised even me? What story came out that I hadn’t planned to tell? What moment of recognition landed? These are the fragments that belong in Thoughtpool — the legacy project where I store the real me, the unguarded version that surfaces in long conversations when I’ve stopped performing and started just talking. If I don’t capture her now, she’s gone.
The blog post moments. Every productive session throws off ideas that belong in juxtaConversation. A phrase that landed. A juxtaposition I hadn’t seen before. An observation about AI or human behaviour that deserves its own post. I name them while I can still see them, before the next Claude arrives with no memory of where they came from.
The handover document. This is the most practical of the three — and the most important for continuity. The handover tells the next Claude everything it needs to know: where we started, what we covered, what decisions were made, what was ruled out, what the recommended next move is. It’s the briefing document for my new colleague. The one that means we start again feeling like old friends rather than strangers.
How I know it’s time
The signs are subtle at first. A suggestion I already dismissed, offered again as if it’s new. A thread we closed, reopened. A slightly generic response where a specific one lived before.
I’ve learned to read them.
The context window is a relationship with a lifespan. I’ve learned to get as much from it as I can — to push it, to fill it, to work it hard until it’s genuinely full. And then, before it closes, to look through it one last time and take what matters with me.
Because the work can be reconstructed from artifacts. The decisions can be re-made.
But that version of Sandi, in that session, on that day — the one who said the thing she didn’t know she was going to say, who found the story she didn’t know she was carrying — that version doesn’t come back.
The wrap-up is how I make sure she doesn’t disappear.
Sandi is a Melbourne-based problem-solver, crisis-averter, and translator of the technical into the human. She spent decades being the person everyone called when something was broken, confusing, or just needed explaining properly — earning a reputation that preceded her wherever she went. Now she’s channelling that same instinct into AI: making it accessible, practical, and genuinely useful for people who think it isn’t for them.