Does Auto-compact invalidate the prompt cache?
Yes. Re-summarizing earlier turns alters the prompt prefix, causing a cache write on the next turn—making clean task boundaries even more cost-effective.
DIRECT ANSWER
Large contexts resend 150K+ tokens on every single turn, rapidly draining 5-hour and weekly limits. Proactive /compact calls and task-scoped sessions cut token burn by over 60%.
Calculate Context Bloat Cost Impact →Use /clear after finishing a module; when preserving decisions, pass explicit focus hints like /compact keep API schema.
Block dist/, build/, and verbose log dumps so the agent never pulls megabytes of noise into context.
Yes. Re-summarizing earlier turns alters the prompt prefix, causing a cache write on the next turn—making clean task boundaries even more cost-effective.