Claude Code Desktop Adds Nested Sessions and Saved Environments

Anthropic has updated the Claude Code desktop app with nested sessions, reusable environments, a redesigned launcher, and clearer status indicators. The changes help developers run several Claude tasks at once while keeping their output, context usage, and pending changes visible.

Claude Code desktop already supports parallel sessions with Git worktree isolation. A worktree gives each session a separate checkout of the repository, reducing file collisions between concurrent tasks. Anthropic covers the initial setup in its desktop quickstart and explains the broader workflow in the desktop guide.

Child sessions clear the main thread

A parent session can now split parallel work into nested child sessions. Each child handles its assigned task and reports the result to the parent when finished, keeping most intermediate tool calls out of the main transcript.

Developers previously had to open and track separate top-level sessions for each stream of work. The new hierarchy lets one session coordinate the split, preserving a readable record of the original request and the completed results.

Save a workspace once

The redesigned launcher puts recent folders within one click and lets developers save a configuration as a reusable environment. An environment can include multiple folders, an SSH host or cloud target, and an optional worktree for each folder.

A saved environment records that setup as a named preset. Worktree options remain useful for repositories where several sessions may create branches or edit nearby files, although developers still need to review and merge each branch.

A dashboard for agent state

The session view now exposes the information needed to supervise concurrent work:

• Session status: The sidebar distinguishes active sessions from those waiting for input.
• Live plan: A to-do list shows the steps Claude currently intends to execute.
• Turn recap: A summary card appears when Claude pauses for a response.
• Runtime details: A side rail shows the execution environment, context usage, and pending changes.

The context meter shows how much of the model’s working window a session has consumed. A developer can finish the current task, summarize progress, or start a fresh session before a long transcript crowds out relevant instructions and code.

The live to-do list reflects Claude’s current plan and may change as tools return new information. Logs, diffs, tests, and generated files still require review before changes are accepted.

Side questions get separate sessions

Claude can now suggest follow-up work while a task runs, and any suggestion can be promoted to its own session. This gives related work an independent transcript, context window, and execution state.

The new /btw command opens a side question in another tab while the original session continues. The resulting tab remains available as a regular session, allowing the developer to ask follow-up questions without adding unrelated context to the running task.

Access, setup, and usage

Anthropic distributes the update through the regular Claude desktop app. Claude Code requires a Pro, Max, Team, or Enterprise subscription. The app is available for macOS and Windows, with Linux support in beta.

1. Update the Claude desktop app.
2. Open the Code tab.
3. Create a session or reopen a saved environment.
4. Ask Claude to split independent tasks, then monitor the child sessions from the sidebar.

The new controls do not require a separate add-on, but every active session consumes model usage. Parallel requests can reach plan limits or rate limits sooner, while local sessions and worktrees also use system memory and disk space.

Choose clean task boundaries

Parallel sessions suit work that can be divided into independent streams with explicit inputs and expected outputs. Useful patterns include:

• Implementing a feature in one session while another runs tests and investigates failures.
• Building frontend and backend changes against an agreed API contract.
• Refactoring stable code while a separate session updates its documentation.
• Maintaining a release branch alongside an experimental implementation.

Tasks that edit the same files, depend on unsettled design decisions, or require frequent coordination can create merge conflicts and duplicated work. Clear ownership of files, branches, interfaces, and test commands gives each child session a defined boundary.

The workable number of concurrent sessions depends on plan limits, machine resources, repository size, and the developer’s capacity to review results. The interface can display many sessions, but each additional stream adds diffs, decisions, and potential conflicts that need human attention.

Coordination moves into the app

Claude Code desktop now handles more of the coordination around parallel coding work. Nested sessions organize task decomposition, saved environments remove repeated setup, and the status interface shows where intervention is needed.

Developers remain responsible for defining task boundaries, checking generated changes, resolving conflicts, and approving the final result. The update makes those responsibilities easier to track when several Claude sessions are working at the same time.