← Blog

Claude Code 8 min read

Never explain the same thing to AI twice

AI conversations end and an hour’s best work goes with them. This AI saves what matters after each task, logs it, backs it up, and resumes where you left off.

Claude CodeGitHub

Illustration for the article: Never explain the same thing to AI twice

What you’ll take away

You keep explaining the same things to AI over and over, because every conversation ends and takes everything with it. In a few minutes of reading, you’ll know how to recognize an AI that saves what matters on its own, and why you can trust it.

  • I’ll show you where the most expensive loss hides when an AI conversation ends.
  • You’ll get a one-minute self-test.
  • You’ll see what an AI should save from a conversation and what it should throw away.
  • And you’ll learn who gets real value from an agent with its own memory, and who doesn’t need one.

Every conversation with AI has one quiet flaw: sooner or later, it ends. And the most valuable part of an hour’s work disappears with it. Not the data. You’ll save that. What disappears are the decisions: why you did something exactly this way, which approach worked, and which one was a dead end.

It’s Monday morning. You open a project you spent two hours on with AI last week, and the AI knows absolutely nothing about it. Once again, you explain what it’s about. Once again, you describe why you decided to do it that way back then. And neither of you remembers the small detail you finally figured out together after an hour of trial and error.

Lost decisions cost more than lost time

Four-panel meme: a man in a suit at a flip chart excitedly says “I’ll solve it with AI.”, then, pleased, “Done. Closing the window.” In the third panel he realizes in horror: “Three weeks later: same problem.” In the fourth he stands helplessly with a colleague above the caption “And nobody knows how we solved it back then.” It’s about a decision nobody wrote down, which is why you end up paying for it twice.

Jumping back into the project costs you ten minutes of getting your bearings. But that’s not the expensive part. What’s expensive is the lost decisions: the trick you once worked hard to figure out, which you’re hunting for again three weeks later because nobody wrote it down. You pay twice for the same thing.

Stateless (memory that lasts one conversation)

The property that makes a machine remember nothing at all between two conversations. That’s not because the model is dumb. It simply starts every conversation with a clean slate. Everything it needs to know next time, you have to supply again, or it has to get saved somewhere outside the conversation on its own. Until you solve that, there’s only one person keeping the project’s memory: you.

This bugged me long enough that I finally did something about it. I have dozens of conversations with AI every day, and in each one I make a decision that will still matter tomorrow. But the moment I closed the window, it vanished along with everything else.

Meme: a man asleep in bed under a glowing screen showing a brain and a jittery line. During the day he thinks “I remember that decision.” with his brain at 2%; at 3:00 a.m. he’s jolted awake by “…or did we do it differently back then?!” with his brain at 140%. A decision that lives only in your head falls apart the moment you’re unsure.

One-minute self-test

Take a project you’re in the middle of and try saying out loud: why did we choose this particular solution, and what have we already tried that didn’t work? How much of that is down in black and white, and how much is only in your head? Every answer you can find only in your memory is one more place where it all gets lost the moment you’re swamped, or on vacation.

A wrap-up after every task

Meme: a man in a suit turns away in disgust from the caption “Re-explaining the same thing to AI from scratch.” and points approvingly at “The wrap-up saves what’s still true six months later. You don’t have to ask.” The joke pits endless re-explaining against an agent that saves what matters on its own.

The fix is to stop taking notes by hand and leave the whole thing to the agent. After every finished task, the agent runs a wrap-up: it goes through what we just did on its own and pulls out only what lasts.

A decision, and the reason it went the way it did. An approach that proved itself. A correction I gave it while we were working.

What happens after every finished task

Trigger
The task is done
→
Wrap-up
The agent reviews the conversation
→
Distill
It pulls out only what lasts
→
Saved
Memory, log, and a backup on GitHub
The decision, the reason, and the approach that worked all get saved on their own. The noise gets thrown out.

What gets saved is the distilled version: a few sentences that will still be true six months from now, not a transcript of the whole conversation.

The agent also makes sure it never writes the same thing down twice. So instead of growing into a mess, the memory keeps itself clean. It runs on its own, every time, on the same principle as an AI that checks its own work.

A log and a backup you never have to think about

Meme asking “Who holds your project memory?”: on the left, a desperate man in a suit among flying papers above a box of binders, labeled “Your head: 14 tabs, notes, ‘I know this’”; on the right, a calm man with a book and a small robot writing in a log, labeled “Agent with a log: logs every step, off-site backup.” At the bottom: “Which one are you?”

Alongside the distilled knowledge, every step adds a line to the project log: when it happened, what we did, and why. Anyone who has ever tried to keep an honest work log knows how that goes: you write for the first week, then you stop. Here, that discipline has moved to the agent, which never gets tired. When someone asks six months from now why we did it that way, the answer is right there on a line, not lost in a fog.

Meme: a terminal window showing the agent’s wrap-up. The agent reads a conversation 2 hours 14 minutes long, saves 3 decisions to memory, adds a line to the project log, pushes a copy of the work to GitHub, and discards 1,842 lines of noise. It ends with “Done. Tomorrow you’ll pick up right here.”

Just as automatically, every change goes straight off my computer. After every finished task, a copy of the work sits safely on GitHub, not just on a drive that might not wake up one morning. For texts and decisions that are hard to recreate, that’s the kind of peace of mind you only appreciate at the moment you would otherwise have lost them.

Why you can trust this kind of memory

Automation that writes to its own memory sounds like a recipe for trouble. What if it saves nonsense and follows it next time? That’s why a person has the last word here too.

Human in the loop

A way of building automation where the system prepares everything, but a person confirms the deciding step. In practice, it’s the only difference between an automation you trust and one you’re afraid of.

Catching up on where you left off last time

Raw transcript of the whole conversation
2 hours
Distilled: a few sentences that still hold
1 minute
The agent saves the distilled version, not the raw transcript. A month later, you read the memory in a minute instead of picking through two hours of conversation.

Sometimes I don’t want it to remember something. I say “don’t save this,” and the whole wrap-up gets skipped that one time. I make the call, not the system’s momentum.

Who doesn’t need this

When an agent’s own memory pays off

Worth it

  • You run several projects at once
  • You have long conversations and lose the thread between them
  • You switch between topics and something always slips through

Not worth it

  • You solve one thing from start to finish in a single session
  • You have nothing to carry over to next time
The more threads you hold at once, the sooner an agent’s own memory pays for itself.

One more distinction, so nothing gets mixed up: this article is about how the agent saves what matters on its own after every step. The fact that it can then tell you right away where you left off last time is just the result of this layer. The same principle also holds up a bigger company memory built on top of your data.

The whole system in a nutshell

  1. The agent runs right where I work, not as a separate tool on the side.
  2. After every finished task, it stops on its own and does a wrap-up.
  3. It pulls only what lasts out of the conversation: the decision, the reason, the approach that worked. The noise gets thrown out.
  4. It adds a line to the project log and makes sure it doesn’t write the same thing down twice.
  5. It sends a copy of the work off the computer, to a backup on GitHub.
  6. When I say “don’t save this,” the wrap-up is skipped that time.

Monday morning: before and now

Before

Ten minutes just to get your bearings in the project
You explain again what it’s about and why it’s done this way
Three weeks later, you’re hunting for last time’s trick again

Now

“We left off here.”
The AI reads the log and is back up to speed
It has the decision and the reason in black and white
What used to be ten minutes of getting your bearings and hunting for lost decisions comes down to one sentence and one second.

There’s no magic behind it: just an agent working alongside you that cleans up after itself at every step. And that Monday morning? You open the project and the AI is back with you within a second, including the small detail the two of you figured out after an hour back then. Conversations still end, just like before. They just don’t take anything with them that you’d hate to lose.

FAQ

What does it mean for an AI to keep its own log?

After every finished task, it writes down in the project record what we did and why. It’s not a transcript of the whole conversation, just a few sentences that will still hold months from now. You don’t have to ask for anything; it happens on its own.

How is this different from an AI that remembers where you left off?

This is the layer underneath: the mechanism the agent uses to save what matters after every step. Picking up where you stopped is the result. Without the saving, there would be nothing to pick up from.

Won’t that memory fill up with clutter within a month?

No. The agent makes sure it doesn’t write the same thing down twice, and it throws away the working noise of the conversation. It only saves what lasts, so the memory tends to get cleaner rather than grow into chaos.

What if I don’t want it to remember something?

You say “don’t save this,” and the whole wrap-up gets skipped that one time. You have the last word, not the system’s momentum.

Who is it worth it for, and who doesn’t need it?

It pays off once you’re running several projects or long conversations where you lose the thread in between. If you solve one thing from start to finish in a single session, an agent with its own memory won’t give you anything.

Want something like this?

I built this system to order, and I can build one for you too. Tell me what caught your eye.

Keep reading

Looking for something specific?

Describe what you’re dealing with in one sentence, and I’ll find the articles that help.