PRODUCTION SCENARIO
Your autonomous coding agent needs several context windows to port a 300-test service, running unattended with no engineer between windows. The first window wrote a tests.json tracker and an init.sh setup script and has been committing as it goes, so the framework already exists and the files and git log are current. Each later window is handed a compacted summary of the one before it, and those windows keep re-implementing modules that already pass.
How should the later windows be started?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Start each later window fresh, pointed at tests.json, init.sh and the git history
When a context window is cleared, a brand new window beats a compacted summary: current models recover state from the local filesystem, and tests.json, init.sh and the commit history are ground truth rather than a retelling. A richer summary is right when there is no durable state on disk to read; here there is, and a summary listing every module grows toward the limit it was meant to relieve. Re-running the setup prompt is right for the very first window, which has to build the framework, and init.sh already does that. A hand-written summary is right when a person is in the loop, and this run is unattended.