strategic-compact

Context preservation in long-running sessions is achieved by prompting manual compaction at logical task boundaries, using hook-driven flows to retain essential memory while discarding redundant data. This minimizes context loss during multi-phase workflows like research, planning, and implementation.

Context compaction should be triggered at logical phase boundaries and milestone transitions, such as moving from research to planning or implementation to testing. Configurable thresholds and periodic reminders prompt compaction at these meaningful milestones to maintain workflow continuity.

Configuring Claude hooks for strategic compaction involves setting up the strategic-compact script to trigger at logical phase transitions. You establish configurable thresholds that prompt manual compaction, preserving essential information while removing noise without interrupting critical work.

Manual context compaction does not disrupt active task execution because it is applied at logical task boundaries. By prompting compaction at milestone transitions, it reduces cognitive load and discards redundancy without interrupting critical work in progress.

The best way to manage context loss during phase transitions is using hook-driven strategic compaction. This approach applies manual compaction at logical boundaries with configurable thresholds, ensuring essential memory is preserved while redundant data is removed.

Strategic compaction is designed for long-running sessions with multi-phase workflows. For short, single-phase coding tasks, manual compaction at milestone transitions is unnecessary because context growth remains manageable without discarding redundant data.