Long AI sessions do not usually fail in one dramatic moment. They drift. The agent remembers an outdated plan, confuses a previous file with the current one, repeats a corrected mistake, or keeps stale investigation details while the real decision falls out of focus.
The mistake is treating context like a backpack: keep adding material because it might be useful. Context is not a backpack. It is a budget. Every log, file, correction, and side conversation competes with the decisions the agent must still hold accurately.
What deserves to stay
A good session preserves decisions, changed files, verification commands, open blockers, and the next two actions. It does not preserve every path explored or every dead hypothesis in the main working memory. Broad investigation should be summarized. Side findings should be written down. Unrelated tasks should start clean.
This is especially important with AI agents because they can sound coherent while operating from stale context. The human sees confident prose. The repo sees a wrong assumption.
The handoff document is not a status report
A handoff exists so a fresh session can resume cold. It should name the branch, last commit or PR, files changed, decisions made with reasons, what is in flight, verification status, and the next two actions. It should be factual enough that the next agent does not reopen settled debates or repeat completed searches.
If the session is getting long and the task is still important, a clean restart with a precise handoff often beats pushing through. You are not losing momentum. You are paying down context debt before it becomes rework.
The correction threshold
When an agent has been corrected on the same point more than twice, stop treating it as a local misunderstanding. The session is probably polluted. Clear, compact, or restart with a sharper prompt and the few facts that must survive.
Good context hygiene feels slower because it interrupts the stream. It is faster because it prevents the stream from carrying the wrong assumptions forward.
Series linkage
Part 8 of 10 in Prompt Library to Operating System. Tests preserve behavior; handoffs preserve intent when the session itself gets long.
About AmanERP
AmanERP's development process treats context as an operational resource because durable business software is built across many sessions, not one heroic transcript.