strategic-compact

Context preservation during long multi-phase tasks is achieved by triggering strategic compaction at logical phase boundaries, freeing resources while keeping critical session context intact. This prevents automatic truncation from losing essential milestones.

Compaction should occur at logical boundaries like exploration milestones or phase transitions rather than on a fixed schedule. Prompting users to compact context after completing planning or testing phases maintains coherence across long workflows.

Compaction prompts are configured using thresholds and regular reminders triggered during session activity. A lightweight hook-style integration runs during PreToolUse to monitor context size and prompt compaction when it grows too large.

Session compaction requires no external services to function. It relies entirely on internal session activity, milestones, and user prompts to trigger compact decisions and maintain context integrity without external dependencies.

The best way to maintain context integrity is applying strategic compaction prompts after exploration, milestones, or phase transitions. This preserves critical context while freeing resources during implementation and testing without interrupting automation.

Context coherence is lost during long automation workflows when relying on automatic truncation instead of strategic compaction. Applying compaction at logical boundaries preserves essential task context and prevents session fragmentation.