One endless chat eventually mixes valid decisions with rejected paths. A project conversation that never resets becomes slow and ambiguous over time.
Create a Scratch handover and start the next phase in a fresh chat within the same space.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Summarize this long chat into valid decisions, rejected assumptions, relevant files and a new starting prompt.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to files, sources, responsibilities and expected output format. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not expect the model to know which old statements no longer apply.
The space keeps continuity while the chat regains focus.