Continue an AI task in a new chat without losing the brief

To continue a task in a new AI conversation, bring a short current brief and the relevant source material. Do not assume the new chat can see the old one. Preserve the facts and decisions that matter, then name the next step. A fluent summary can still leave out the detail that changes the work.

Save the current state rather than the whole conversation

A long chat can contain superseded instructions, abandoned ideas, and corrections. Copying all of it may make it harder to see what is current. Start with the result you are working toward and the latest agreed constraints.

For a fictional invitation draft, you might have changed the date twice during the conversation. The handoff should name the confirmed date and explicitly say which earlier dates to disregard. It should not describe all three as equally valid options.

Use this handoff template

Task: [what I am trying to finish]
Current output: [draft or file version]
Confirmed facts: [information I can support]
Current decisions: [choices already made]
Superseded instructions: [earlier directions to disregard]
Unresolved questions: [facts or choices still missing]
Sources to use: [relevant files or excerpts I am supplying]
Next step: [one specific piece of work]
Before continuing, state the current constraints and flag missing inputs.

Keep the source material when the wording matters. A summary saying “the letter has a deadline” is not enough to preserve the exact date, condition, or page location.

A fictional task handoff

You are editing an event invitation. The current draft names October 18 at 6 p.m. The venue is confirmed, but the room number is not. An earlier draft used October 11.

A useful handoff says: “Use October 18, 6 p.m.; disregard October 11. Keep the confirmed venue name. Leave the room number as a question. Next, shorten the invitation without changing those details.”

The new conversation can then continue the edit within a clear boundary. If it supplies a room number or restores the older date, the brief gives you something specific to correct.

Review an AI-generated summary before using it

Ask the old conversation to prepare a handoff if that helps, but read it against the latest draft and source files. Summaries can omit an exception, merge different alternatives, or repeat an earlier mistake.

If the old conversation is unavailable, prepare the handoff from your saved files. Say which information you no longer have rather than asking the model to reconstruct the previous discussion.

Reattach what the new chat needs

Check the new app's actual file and context capabilities. A local filename written in a brief does not give the AI access to the file. Supply the relevant material through the supported path and avoid copying private details that do not help the task.

For code, include the relevant component and the current error or request. For a document, include the exact passage with a location. For a comparison, include the comparison basis and the source for each value.

Keep a brief as the work changes

Update the handoff when a decision or input changes. A current one-page brief can be useful even when you stay in the same conversation. It helps you inspect the next answer without relying on the model to remember every correction from a long exchange.