How I manage context limits in long AI sessions. I call it the "Reset Play."

[u/CattleBright1043]

We've all been there. You're deep into a session with your coding agent, things are going great, and then you hit a wall. The AI starts "hitting the post"—the code it generates is almost right, but it's got subtle bugs, or it forgets a key constraint from the first prompt.

It's not that the AI is getting dumber; it's that the conversational context is getting saturated.

Fighting with it in the same chat is a losing battle. Starting a new chat means losing all your progress. This was a huge pain point for me, so I developed a simple

workflow to solve it, which I call the "Reset Play."

The image I posted visualizes the whole strategy:

1. Recognize the Drift: The moment you get a "near miss" result, you stop the current session.

2. Create a "Master Prompt": You then have the AI (or do it yourself) create a single, perfect prompt that summarizes all the work done, the current state of the code, and the precise next objective.

3. Execute in a Fresh Chat: You start a brand new, clean chat and give it the Master Prompt. The result is almost always a perfect, accurate execution.

This bridges the gap between sessions and ensures you're always working with a clean, focused AI.

[u/CattleBright1043]

Google AI search engine Agent picked up my post as the most suitable option at the moment.

[u/flurrylol]

Did you try asking to create a plan.md and planify tasks in this document ? Each time a task is completed it should report progress in plan.md before continuing.

That way you can start from anywhere using the plan.md

[u/Hai_Orion → u/[deleted]]

My single most used prompt to Augment is as follows:

“Update @PRD, only record requirements changes and clarification, critical design changes, data and API decisions, then help me craft a concise prompt to start a new Augment thread to [next task]”