Claude Code's new parallel and nested sessions speed up coding, but they multiply usage. Here's what that means for Pro vs Max plan limits.
What changed in Claude Code, and why does it affect usage limits? #
Anthropic updated the Claude Code desktop app to make running multiple sessions at once faster and easier to manage. The update adds saved environments, nested sessions that spin off sub-tasks automatically, follow-up task suggestions, and a sidebar that groups sessions by status. All of this makes it trivially easy to have several agents working at once, which is exactly the problem: every session, and every nested session underneath it, consumes its own share of your usage quota. More parallelism means more tokens processed, and Anthropic did not announce any changes to usage limits alongside this feature.
TL;DR #
- Nested sessions let a main Claude Code session spawn separate sub-sessions for individual tasks, each consuming quota independently before reporting results back to the parent session.
- Environments let you save a group of folders, an SSH host, or a cloud setup once, so you can launch new sessions into a known working context without reconfiguring each time.
- The sidebar now sorts sessions into three groups (needs input, working, completed), making it easier to track many sessions at once, though some users find sessions jumping between groups confusing.
- Idle compaction automatically summarizes long-idle conversations right before the prompt cache expires (around one hour), so resuming a session doesn’t force Claude to reprocess the entire conversation from scratch.
- Pro plan users will likely hit usage limits quickly with this workflow, since running several parallel and nested sessions multiplies token consumption well beyond single-session use.
- The feature is effectively built for Max plan subscribers , since heavier usage ceilings are what make running multiple simultaneous sessions practical.
- User feedback flagged missing pieces , including the removed effort slider, harder-to-find GitHub PR buttons, and no way to view sessions across devices without remote control setup.
Seven tools to build an app. Or just Remy. #
Editor, preview, AI agents, deploy — all in one tab. Nothing to install.
How do nested sessions work, and why do they cost more? #
When you ask Claude Code to handle several tasks at once, it now creates a separate nested session for each one instead of cramming all the output into your main chat. Each nested session runs independently, processes its own context, and sends a summarized result back to the parent session once finished. In a demo covered by the creator, a main session titled “fix product grid layout shift” spawned two nested sessions, one for lazy- images and one for setting image dimensions on cart thumbnails. Both appeared under the main session in the sidebar and reported back when done.
This is a real usability improvement. Before, parallel work flooded the main chat with raw output, making it hard to follow what happened. Now the main session only sees the final result, while you can still drill into any nested session for details. But each of those nested sessions is a full Claude Code session under the hood. It processes conversation history, runs tool calls, and consumes tokens just like a standalone session. Three nested sessions running alongside a main one effectively means four sessions worth of usage, not one.
What is the /btedu command and how does it affect session load? #
The /btedu command lets you ask a side question in the middle of a running session without interrupting it. Typing /btedu followed by a question opens that question in a new tab, while the original session keeps working uninterrupted. This keeps side questions from cluttering the main conversation thread and stops Claude from pausing its primary task to answer something unrelated.
Like nested sessions, this is a quality-of-life win for organization, but it’s also another session running in parallel. If you’re already juggling several working sessions and spin off a few /btedu tabs for quick questions, you’re adding to the total load against your usage limit, even if each individual tab is short-lived.
Which Claude Code plan do you need for parallel sessions? #
The transcript doesn’t give exact token or request caps for Pro versus Max, but the practical guidance from early usage is straightforward: this workflow is built for Max plan subscribers. Running even a handful of parallel sessions, each potentially spawning nested sub-sessions, adds up fast. On the Pro plan, user reports suggest you’ll hit your usage ceiling quickly if you try to replicate the kind of multi-session workflow shown in Anthropic’s own demo.
Anthropic did not announce any limit increases tied to this update. The new sidebar, environments, and nested session features are about making parallel work easier to manage, not about making it cheaper. If your plan already caps how much you can do in a single session, adding more simultaneous sessions just hits that ceiling sooner.
What is idle compaction and how much does it actually save? #
Built like a system. Not vibe-coded.
Remy manages the project — every layer architected, not stitched together at the last second.
Idle compaction addresses a specific inefficiency in how Claude Code handles long-running, d sessions. Claude Code relies on a prompt cache that stores the processed state of your conversation so follow-up messages don’t require reprocessing everything from scratch. That cache expires after roughly an hour of inactivity. If you step away from a session and come back after the cache has expired, Claude has to reprocess the entire conversation history, which eats into your usage quota even though you didn’t send a single new message.
Idle compaction fixes this by automatically summarizing an idle session right before its cache expires. Instead of the full conversation history, Claude only needs to process a condensed summary when you return. In the terminal, this shows up as a message noting the session was “compacted while idle before the prompt cache expired.” Anthropic has said this saves users some usage but hasn’t published a specific percentage or token figure.
This matters more as parallel sessions become the norm. If you’re running five sessions and actively working in one, the other four are sitting idle, racking up cache-expiration risk. Idle compaction quietly protects against that waste, making multi-session workflows somewhat more sustainable than they’d otherwise be.
Is the parallel session update worth using right now? #
For heavy users already comfortable running multiple coding agents, yes, with caveats. Nested sessions and /btedu tabs solve a genuine problem: long sessions get cluttered and hard to follow. The new sidebar grouping (needs input, working, completed) gives a quick-glance view of what needs your attention across many open sessions. Idle compaction is a sensible efficiency fix that costs you nothing. But the update has rough edges. Some users report the effort slider, a control some relied on, appears to have been removed or hidden. GitHub PR buttons are reportedly harder to find in the redesign. Some sessions moving between status groups on their own has confused users managing ten or more sessions at once. And requests for features like grouping sessions by project, multi-account support, or viewing laptop sessions from a phone without setting up remote control remain unaddressed.
The bigger question is usage limits. The features make it easy to run far more simultaneous Claude activity than before, but the underlying quota structure hasn’t changed. Unless Anthropic adjusts limits or pricing for heavy parallel use, the people most excited about this update, who want to run ten sessions at once, are the ones most likely to hit a wall fast.
Frequently Asked Questions #
Do nested Claude Code sessions count separately against my usage limit?
Yes. Each nested session processes its own context and tool calls independently before reporting a result back to the main session, so it consumes quota on top of whatever the parent session uses.
Can I use parallel sessions on the Claude Code Pro plan?
You can, but you’re likely to hit usage limits quickly if you run multiple sessions with nested sub-tasks. The workflow is better suited to the Max plan, which allows for heavier usage.
What does idle compaction actually do?
It automatically summarizes a session’s conversation history right before the hourly prompt cache expires, so resuming the session later only requires processing a short summary instead of the full conversation.
Did Anthropic increase usage limits alongside this update?
No. The update focused on session management, organization, and the user interface. No changes to usage limits or rate caps were announced.
What happened to the effort slider in Claude Code?
Everyone else built a construction worker.
We built the contractor.
One file at a time.
UI, API, database, deploy.
Several users reported that the effort slider appears to have been removed or hidden in the redesigned interface, and it’s a commonly requested feature to bring back.