strategic-compact

To manage context during code workflows, you can manually trigger context compaction at strategic intervals. This preserves relevant context across task phases instead of relying on arbitrary auto-compaction that might interrupt your execution.

Manual context compaction is best used at strategic intervals, such as after exploration, before execution, or after reaching milestones. This prevents mid-task interruptions that often occur with automatic compaction thresholds.

You can prevent mid-task interruptions by triggering manual compaction after a configurable threshold of tool calls. This ensures the context is compacted at a logical breakpoint rather than unexpectedly during an active task phase.

Yes, context compaction can be configured to trigger after a specific threshold of tool calls. This allows you to fine-tune memory management and maintain relevant context before hitting automatic limits.

The best way to maintain context across task phases is to use strategic manual compaction. By compacting after exploration and before execution, you control what context is preserved, optimizing memory usage for the next phase.