strategic-compact

To prevent context drift in long-running workflows, use strategic compaction at logical phase boundaries. A PreToolUse hook counts tool invocations and triggers periodic compaction reminders, ensuring deliberate context resets instead of relying on automatic compaction.

Yes, you can configure the compaction threshold by setting the COMPACT_THRESHOLD value, which defaults to 50. After reaching the threshold, the PreToolUse hook issues periodic compaction reminders every 25 tool calls to manage context.

The best way to manage context across research and implementation phases is to use a PreToolUse hook that enforces strategic compaction at logical task boundaries. This prunes context and preserves the essential plan when transitioning between phases.

You can integrate compaction reminders by adding the strategic-compact skill to your existing hooks.json and suggest-compact.js files. This connects the PreToolUse hook to count tool invocations and keep workflows lean.

You should use strategic compaction instead of auto-compaction during long-running, multi-phase workflows like planning and testing. It provides deliberate, phase-boundary resets to preserve essential context, whereas auto-compaction often causes context drift and bloated session memory.