PRODUCTION SCENARIO
A migration agent works on a codebase across several sessions spread over a week. Each new session currently re-explores the repository and repeats earlier decisions before doing any new work.
How should the agent carry state between sessions?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Memory files holding a progress log and feature checklist, read at each session start
The memory tool's multisession pattern has an initializer session write a progress log and a feature checklist, later sessions open by reading them, and each session update the log before it ends. Replaying the old transcript reloads the whole history into context every time, the cost the pattern exists to remove. A week-long session still fills its context window and loses everything unwritten on any interruption. Compaction summarizes the conversation it is in; it does not start the next one.