strategic-compact

Manual context compression at workflow boundaries is enforced by configuring PreToolUse events to trigger the suggest-compact.sh hook and setting the COMPACT_THRESHOLD parameter. This approach preserves execution plans and critical decisions across multi-step tasks by avoiding automatic context drift.

Automatic context compression causes information loss and logic misalignment in long-running processes because it lacks awareness of logical boundaries. Manual compression at strategic milestones ensures the next phase remains controllable by retaining critical context, execution plans, and key decisions between phases.

You need manual context compression for multi-step tasks involving long workflows, cross-team collaboration, or tasks requiring rollback and audit capabilities. It enforces context cleanup at logical boundaries between milestones, ensuring the next phase remains controllable and context is preserved.

Yes, manual context compression integrates directly with PreToolUse hooks for milestone tracking. By triggering the suggest-compact.sh script through PreToolUse events and configuring the COMPACT_THRESHOLD, you coordinate compression precisely at workflow boundaries between milestones.

Automatic context management lacks the ability to recognize logical boundaries between milestones, leading to uncontrolled context drift and lost critical decisions. For cross-team collaboration and audit-ready tasks, manual compression at strategic boundaries is required to preserve execution plans and ensure phase controllability.