The Session Memory Loop

Claude doesn’t remember yesterday. You have to teach it to. And the way you teach it is not by restating everything — it’s by building one small file that does the restating for you.

Every session starts from zero

Claude’s context window is powerful, but it resets. Every new session, you’re starting over. If you don’t address this, you spend the first ten minutes of every conversation re-explaining your situation, your project, your preferences, and your current state — before you can do anything useful.

Most people deal with this by just repeating themselves, or by keeping one long chat open until it gets unwieldy. Neither works well. Repetition is wasteful. A single endless session accumulates noise and eventually bogs down.

The fix is a session memory file.

What a session memory file actually is

A session memory file is a short document — usually under 200 lines — that you give Claude at the start of every session. It tells Claude who you are, what you’re working on, what decisions have been made, and what the current state of open threads is.

The key insight is that this file is yours to maintain, not Claude’s. Claude helps you keep it up to date, but you control what goes in it. That distinction matters: it means the file stays accurate even when Claude makes mistakes, because you’re reviewing it.

That’s it. You paste this at the start of each session and Claude immediately has context. No re-explaining.

Keeping it current without effort

The file only works if it stays accurate. The trap is spending more time maintaining the file than you save by having it. The way to avoid this is to update it at the end of each session, not the beginning.

At the end of a session, before closing, ask Claude:

You review the changes, accept what’s right, correct what isn’t, and save. Next session, you start with an accurate file.

The loop is: load at the start, update at the end. Two minutes of friction eliminated in exchange for two minutes of closing work. The math favors it inside of a week.

The discipline of keeping it short

The hardest part of maintaining a session memory file is resisting the urge to put everything in it. A 600-line file that contains every decision ever made is almost as useless as no file at all — Claude has to read through all of it to find what’s relevant, and so do you.

The rule: only include what changes Claude’s behavior in this session.

• Background that never changes (your name, your job title) — keep it, but keep it short.
• Decisions that are truly final — one line each, max.
• Ongoing threads — in detail, because these need attention.
• Historical context — almost never. If Claude needs it, paste it when needed.

When in doubt, leave it out. You can always add it back if it comes up again.

Your first session memory file

The fastest way to start is to let Claude write the first draft from a conversation. Have a session about whatever you’re working on, then at the end ask:

Review it. Fix what’s wrong. Save it somewhere you’ll remember (same folder as your project, or a dedicated notes file). That’s your starting point. The loop starts now.

One session memory file, maintained for three weeks, is worth more than three months of ad-hoc context-pasting. The compounding starts early.

This is Chapter 1 of Patriola’s Guide to Claude: Productivity. The book covers four more areas: inbox triage, task tracking, prompt patterns, and the daily loop that ties it all together.