A coding agent can accumulate pages of test output while working on one bug. Our suggested compacted state preserves the goal, constraints, files changed, checks completed, and unresolved problems. It can drop repeated logs while retaining pointers to the full records.
The terminology varies. Anthropic’s context-engineering guide calls summarizing a long conversation and starting a fresh window with that summary compaction. In episode 53, at 36:33, Richmond Alake uses compaction for moving full context into external storage and retrieving it when needed. Alake distinguishes that approach from lossy summarization. The episode’s sponsor read names Galileo.
Agent memory is the broader question of what persists and how it is retrieved. Compaction manages the active context window. Retaining full records allows later retrieval; a summary alone can discard details.
Our suggested check is to resume from the compacted state and ask whether the agent still respects the original constraints and can recover the supporting evidence. A summary saying “deployment approved” is dangerous if the original approval applied to a different commit. Keeping a concise handoff in context and an auditable full record outside it can serve different needs.
Sources
- Anthropic: Effective context engineering — Describes compaction, structured notes, and the risk of discarding critical context; checked October 7, 2026.
