strategic-compact

To prevent context loss during long-running Claude Code sessions, you can use strategic compaction to prompt manual memory pruning at logical boundaries, which stops arbitrary auto-compaction from eroding essential context.

You should compact context in multi-phase workflows before major transitions, such as moving from research to planning, to preserve essential session state and maintain coherence across unrelated tasks.

You set up strategic context compaction by configuring a hook with a small script that tracks tool calls and triggers prompts at configurable thresholds, reminding you to prune context before major transitions.

Yes, you need a hook configuration and a small script to track tool calls and trigger manual context compaction prompts at logical boundaries within your Claude Code workflows.

Yes, you can configure tool-call count thresholds and phase-change triggers to determine exactly when the system prompts you to perform strategic context compaction during long-running sessions.

Auto-compaction erodes essential context because it triggers arbitrarily based on token limits rather than logical boundaries, causing it to discard critical session information during unrelated task switches or multi-phase workflows.