Claude Code Idle Compaction and Nested Sessions: How to Cut Token Waste

Key takeaways

• Idle compaction runs before the one-hour prompt cache expires, which saves a costly full re-read
• It needs Claude Code v2.1.290 or later, and you can tune the token threshold with an environment variable
• Nested sessions keep tool calls and side work out of your main conversation
• /btw lets you ask side questions without adding clutter to the main task
• Every extra session still uses your plan’s usage, so only split work when the tasks really are independent
• This guide supports our Claude Code update and AI news round-up

The latest Claude Code update was mostly about interface changes. Two of the new features also affect your bill, or how quickly you hit your plan limits: idle compaction and nested sessions.

This guide answers one question: how do you use them to cut token waste without losing the context you need?

What is Claude Code idle compaction?

Idle compaction is automatic summarising that kicks in when you walk away. Anthropic’s Claude Code changelog describes it like this: a terminal conversation of 200K tokens or more that is left idle for about 54 minutes is compacted before its one-hour prompt cache expires. That way, your next message doesn’t have to reprocess everything.

In the video behind our main article, World of AI describes the same feature as roughly “an hour of inactivity”. The precise figures above come from Anthropic.

Why does idle compaction save tokens?

Long conversations are cheap to continue while they are cached. Once the cache expires, the whole history has to be processed again on your next message. For a long session, that is a large and expensive re-read just to say “carry on”.

How do you turn idle compaction on, off or tune it?

1. Update Claude Code. The settings below need v2.1.290 or later.
2. Leave it on if you often step away from long sessions. This is the default behaviour.
3. Turn it off for a project where every detail matters. Add "idleCompaction": false to that project’s settings.json.
4. Change the threshold with the CLAUDE_CODE_IDLE_COMPACT_MIN_TOKENS environment variable. Raise it if you only want very large sessions compacted.
5. Compact on purpose before a break. You can still type /compact yourself to summarise early. This is described in the Claude Code desktop docs.

What are nested sessions in Claude Code?

In the redesigned Claude Code desktop app, you can ask Claude to work on several tasks at once. It then creates a separate child session for each one. When each child finishes, it reports back to your main session, and most of its tool calls stay out of your main conversation.

Some related features help as well:

• Suggested tasks. Claude can propose follow-up work, and you can launch any suggestion as its own session.
• /btw. Opens a side question in a separate tab while the main task keeps running.
• Saved environments. Preset folders, SSH hosts or cloud targets, with optional Git worktrees so each task changes its own copy of the code.
• Sidebar status. Shows which sessions are working and which are waiting for you. Each session has a live to-do list, a recap card and a context meter.

How do you run parallel work without burning usage?

1. Split only independent work. “Build the API” and “write the docs for the agreed API” can run in parallel. “Redesign the same page twice” can’t.
2. Give each child a clear brief. Say which files it may change, what result it should return and how to check that result.
3. Use worktrees for code changes, so child sessions don’t edit the same files at the same time.
4. Send side questions to /btw instead of the main session, so the main context stays small.
5. Watch the context meter. When a session gets close to full, finish the task, summarise it, or start a fresh session.
6. Review every result before you merge. Parallel work means more diffs to check.

What are the trade-offs?

• Compression can lose detail. A summary is shorter by design. Keep important decisions in files, not just in the chat.
• Parallel sessions still cost usage. Every active session uses your plan, so running five at once can hit your limits sooner.
• The model selector has moved out of sight. World of AI noticed it is missing from the new desktop interface, so check which model each session is using.
• More sessions mean more review work. The app can show many sessions, but you still have to check and merge what each one produces.

Frequently asked questions

The bottom line

Claude Code idle compaction stops you paying to re-read a long conversation after a break. Nested sessions keep parallel work out of your main context. Keep compaction on for everyday work, turn it off where detail is critical, and only split genuinely independent tasks. For the wider update, read Fable 5.5 Release Rumours, OpenAI Spy Arrest and a Big Claude Code Update.

Related posts

• Fable 5.5 Release Rumours, OpenAI Spy Arrest and a Big Claude Code Update
• Claude Code Mods: How to Build Your Own Automation Shortcuts
• How to Write a Claude Code Mod Prompt That Actually Works

Garry Knight

I'm Garry Knight, the person behind Prodify Digital. I write about email list building, email marketing, SEO, AI search and the tools that connect them. My aim is to make online marketing easier to understand, so creators and small business owners can make informed decisions about building an audience and keeping people engaged. Here you'll find straightforward guides and product reviews that explain what something does, where it fits and which limitations matter. The focus is on clear explanations and useful next steps—not hype, shortcuts or promises of easy earnings.

See Full Bio