Skip to main content
Master Claude

LESSON 5 OF 5

Run long work without losing the thread

BY THE END OF THIS LESSON

Keep quality steady across a task that spans days.

Long threads drift

A conversation that runs for hours accumulates its own history — including your abandoned ideas, corrections that were later reversed, and dead ends. All of it stays in view and all of it influences what comes next.

This is why a session that started sharp can feel muddled by the end.

Checkpoint deliberately

At natural boundaries, ask for a handover: what has been decided, what is still open, what was tried and rejected and why.

Then start a fresh session with that handover as the opening context. You keep every decision and drop all the noise. The rejected-and-why part matters most — without it, the new session will cheerfully re-suggest something you already ruled out.

Write decisions down outside the chat

The durable record should not live only in a conversation. Keep decisions in a document — in the project, ideally — so it survives any single session and you can point at it later.

For agentic work, the same principle applies: have it keep a running notes file it updates as it goes. That file, not the transcript, is the state.

WORKED EXAMPLE

ONE ENDLESS THREAD

A single conversation running four days, in which the same three options keep resurfacing because two were rejected on day one and nothing recorded why.

CHECKPOINTED

End of each session: "Give me a handover for a fresh session — decisions made and why, what is still open, what we tried and rejected with the reason, and the exact next step." Start of the next: paste that in as the first message.

The handover carries the reasoning forward and leaves the dead ends behind. "Rejected and why" is what stops the new session re-proposing what you already dismissed.

YOUR TURN

Produce a handover you could hand to a colleague.

RUN THIS

We are pausing here. Write me a handover for a fresh session. Include: decisions made and the reasoning, what is still open, what we tried and rejected and why, any constraint I mentioned that still applies, and the exact next step. Write it so someone who was not in this conversation could pick it up cold. Do not include anything that turned out not to matter.

What a good result looks like

If you would not be comfortable handing it to a colleague, it is not a good handover — ask it to add what a newcomer would immediately ask.

KNOWLEDGE CHECK

Answer all 3 correctly to complete this lesson.

  1. 1. Why does quality drift in very long conversations?

  2. 2. Which part of a handover is most often left out and most important?

  3. 3. Where should the durable record of decisions live?

REMEMBER THIS

Checkpoint into a handover that records what you rejected, and keep decisions outside the chat.

Go deeper — read the full guide