strategic-compact

To prevent auto-compaction from interrupting mid-task workflows, you can use strategic task compaction to trigger manual compaction prompts only at logical task boundaries instead of random intervals. This preserves critical context like partial implementation state and recent reasoning.

Context management handles phase-aware guidance by using a decision matrix to determine when compaction is appropriate based on your current task phase. This ensures compaction occurs after planning or debugging, preventing context loss during active implementation.

The best way to track tool invocations for session management compaction checkpoints is to monitor the number of tool calls in your session. This identifies natural compaction points where context loss is minimal.

Workflow optimization provides best practice rules clarifying what context persists through compaction and what is lost. To preserve specific context like variable names, you must save important information to files or memory before compacting.

You should not use arbitrary auto-compaction for long development sessions spanning research, implementation, and testing because it often triggers mid-coding. This causes loss of critical context like partial changes and recent reasoning.

Yes, you can use strategic compaction for sessions switching between unrelated work. It satisfies context preservation requirements by prompting manual compaction only at logical task boundaries, ensuring previous task context is safely managed before starting new work.