strategic-compact

You should compact context at logical workflow boundaries, such as after research, before implementation, or after debugging, to preserve important reasoning while keeping sessions lean.

You can identify context pressure by monitoring tool-call counts and threshold reminders, which flag sessions approaching heavier context usage and signal when manual compaction is needed.

The best way to maintain session continuity is to summarize research findings, compact the session at that milestone transition, and begin implementation with a clean, focused context slate.

Manual compaction works better because it allows you to strategically compact at major workflow shifts rather than waiting for arbitrary auto-compaction that might cut off valuable mid-task reasoning.

Yes, you can use context management compaction during task switches in debugging phases, as boundary-based summarization helps preserve useful context across complex, multi-step debugging workflows.