Quick fixes AG-W003
This conversation is past its best
Shared methods · A shared method; linked tool guides explain the exact steps.
This page covers tools outside your selection. You can still read it. Find matching guides
Long chats accumulate dead weight: rejected drafts, stale constraints, old errors. When steering stops working, a fresh start beats another correction.
This chat keeps repeating old mistakes? Here's the quick fix ↓ — the why sits right below it.
Quick fix: This conversation is past its best
Instead of Correct the same misunderstanding for the fourth time in a two-hour conversation.
Try Summarise the current state of this task: what we settled, what's open, the constraints that still hold. Then paste that summary into a fresh conversation and continue there.
Take the conclusions. Leave the wreckage.
Why this works
Everything in the conversation stays in play: the drafts you rejected, the approach you abandoned, the error message from an hour ago. The model keeps weighing all of it, which is why a long chat starts drifting back to ideas you already vetoed. Corrections add more text on top of the pile; a fresh start with a clean summary removes the pile. The summary step is what makes this cheap — you are not losing two hours of work, you are distilling them.
When this applies
The same mistake keeps returning after being corrected, answers echo discarded drafts, or steering that worked an hour ago has stopped working.
Template
Summarise this conversation as a handover: decisions made (with the why), current state, open items, constraints that still apply. I'll continue in a fresh session.
Go deeper
The full signals list and the judgement call is when to start fresh instead of correcting. Why the pile drags on the answer: the context window. And if the chat went bad because it was doing five jobs, that is its own pattern.
Improve next
- Make the next rewrite more useful
Say what was wrong with the last version before asking again.
- One request, five tasks
This may work better as several steps.
Something wrong with this page?
Say what you expected and what you got. That is usually the shortest route to a correction, and it goes on the public issue tracker so the fix is visible.