Long chats go stale: write a restart note and begin again

Somewhere deep into a long conversation, the thread starts to behave oddly. The helper proposes an idea you rejected an hour ago. It answers a question you have since changed. It treats an early draft as the final one.

Nothing is broken. The thread simply holds too many versions of the truth. You then face two poor options: keep going and keep correcting, or start from scratch and explain everything again. There is a third: write a restart note.

Signs the thread has gone stale

• You are correcting the same misunderstanding for the second or third time
• The helper cites a decision you reversed
• Replies get longer but less specific
• You cannot remember what was decided without scrolling
• You have pasted the same background twice

If two of these sound familiar, the thread has done its job and it is time to move on.

The restart note: six lines

1. Goal. One sentence, in its current version, not the version you began with.
2. Decisions in force. Only the ones that still stand, each with a reason in a few words.
3. Rejected. Options you ruled out and why, so they are not proposed again.
4. Current state. What exists now: files, drafts, versions, with their names.
5. Open questions. What is undecided, and who decides it.
6. Next step. The single next action, in one line.

That is the whole note. If it runs past one page, you are retelling the story instead of describing the state.

When not to restart

If the thread still works, leave it alone. A restart has a cost, and a conversation that is long but accurate is fine. Restart when correcting costs more than writing the note, or when you notice that you no longer know what the helper believes.

Who should write it

Be careful about asking for a blind summary of the entire thread. A summary can preserve what was said most often rather than what is still true, and an idea you rejected after long discussion may be the best-represented item in the history.

A better split: you write lines 1, 2 and 6, because they are about your intent. Ask the helper to propose lines 3, 4 and 5 from the thread, and then you correct them. Two minutes of your attention buys a note you can trust.

Illustrative example

This is a hypothetical scene, not a report of a real case. A marketer has a very long thread drafting a launch announcement. Her restart note reads:

• Goal: a three-hundred-word announcement for existing clients, calm tone, one call to action.
• Decisions: lead with the benefit, not the date, because clients asked about the benefit.
• Rejected: humor in the opening; it was tried and felt off.
• Current state: draft four is in a file called announcement-v4; drafts one to three are archived.
• Open: whether to mention the second feature; she decides on Thursday.
• Next: tighten paragraph two to two sentences.

She opens a fresh conversation and pastes the note. The first reply builds on draft four, keeps a serious tone, and asks nothing that was already answered.

The first reply is the test

The first answer in the fresh conversation tells you whether the note worked. Does it use the current draft? Does it avoid the rejected options? Does it ask only about open questions? If not, the missing line belongs in the note, and the fix takes one sentence.

Keep the note alive

• Update the note at the end of each working session and date it
• Keep one note per project, not one per conversation
• Store it where you will find it: the top of the project folder or a notes app
• Delete lines that are no longer true instead of striking them through
• Reread it before you start the next session

What to leave out

Skip the story of how you got here, every intermediate draft, and anything that was only there to be polite. The note describes where things stand and where they are going. History belongs in the archive.

Octuo, our personal assistant for work across AI, tools and specialist services, carries tasks forward across sessions, with context that survives the conversation. Octuo is available for macOS.