Long chats become useful again when the current state is condensed before the next task starts. Large conversations collect drafts, file extracts, side decisions and rejected ideas. Every new request then competes with old context.
Use Scratch as a handover note with goal, valid decisions, relevant files and open questions before continuing in a fresh chat inside 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 conversation for a fresh chat with goal, valid decisions, rejected paths, relevant files and the next question.” 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 copy the whole history forward when only a compact current state is needed.
The space preserves the record while the new chat works with a smaller, clearer context.