The same task, the same reset — with and without Remaind
A long-running agent eventually fills its context window. When the model context resets, what survives? Below: the identical agent task hits the identical reset. One side has nothing on disk; the other ran remaind resume.
Without Remaind
The reset wipes the working state. The fresh agent re-asks what it was doing, re-opens a settled decision, and walks into a constraint the user had already set. The user pays the cost of reconstruction — every reset.
With Remaind
The reset happens the same way — but the goal, the decisions, the constraints, and the next step were on disk. The resume packet loads them into the fresh context and the agent continues where it left off.
Illustrative — a scripted comparison of one agent task across a context reset. Remaind does not run your agent and does not prevent the reset; it is the durable .context/ your agent resumes from. See How it works for the mechanics and Integrate for the code.