strategic-compact

Context compaction preserves context during long Claude sessions by prompting strategic compaction at logical boundaries. It tracks tool invocations and applies compaction post-exploration or before major context shifts to refresh the session state.

Context compaction should be triggered at logical boundaries such as post-exploration, post-milestone, or before major context shifts. It relies on a configurable threshold and periodic reminders to maintain workflow flow without disruptive prompts.

A PreToolUse hook manages context compaction by executing a script that tracks tool calls and issues compaction prompts when a configurable threshold is met. This setup surfaces opportunistic compaction points during active sessions.

Yes, context compaction reminders are configurable to avoid disrupting coding flow. You can adjust the compaction threshold and reminder frequency to maintain session control without interrupting active tool calls.

The best way to reset context after switching between unrelated tasks is strategic context compaction. By applying compaction at logical boundaries, it clears irrelevant exploration data and preserves essential context for the next milestone.

Claude sessions lose track of earlier research after multiple tool calls due to context window saturation. Strategic context compaction prevents this by tracking tool invocations and prompting compaction to preserve essential exploration context.