Let a Long Session Compact Itself While It's Idle, Not When You Resume

On a 200K+ token session resumed after an idle gap, the first turn re-reads a compacted history instead of the full transcript — a large one-time input-token cut on resume, with the smaller base carried on every later turn; near zero if your sessions never sit large and idle. Intermediate 3 min read

A big Claude Code session left idle doesn't auto-compact, so when you return and send one line the whole swollen transcript re-bills at full input price (the cache went cold while you were away). Turn on idle compaction — and tune its token floor — so the history shrinks in the background before you resume.

🔒 Pro tip · Intermediate

Unlock this tip — and 142 more

This is one of 143 advanced, fact-checked tactics reserved for Pro. Get the full 165-tip library, a searchable archive, and a new tip every morning. Free for 7 days, then $9/mo.

Prefer to browse? The 22 Beginner tips are free forever.