The Claude Code desktop app now splits parallel work into nested sessions

What happened

On October 14 the ClaudeDevs account, Anthropic's channel for developer updates, posted a thread about the Claude Code desktop app. The pitch fits in one line: it is now "much quicker to start sessions", easier to split work across several, and you can see what each one is doing. The post passed 1.9 million views within a day. To get the changes, Anthropic says to update the desktop app and start a new session.

What's new

• A faster start. The new session screen keeps your recent folders one click away.
• Environments. You can save a setup, such as a few folders, an SSH host or the cloud, and start sessions in it. Each folder can get a separate Git worktree, an isolated copy of the project, so two sessions don't edit the same files.
• Nested sessions. Ask Claude to run tasks in parallel and it starts a nested session for each one. When a task is done, it reports its result back to the session that started it, so that conversation stays short enough to read.
• Follow-ups in one click. While it works, Claude suggests follow-up tasks, and each can run as a separate session. The /btw command opens a side question in a separate tab while the original task keeps going.
• A sidebar that shows who needs you. It marks which sessions are working and which are waiting. Inside a session, a live to-do list follows Claude's plan, a recap card sums up the turn when Claude stops for you, and a rail beside the chat shows where the session runs, how much context it has used and what it changed.

Some of this builds on what the app already did: the desktop docs describe running local, cloud, SSH and WSL sessions side by side, opening two in split view and giving a session its own worktree.

What users are saying

Reactions collected by daily.dev are mostly positive about running agents in parallel. The complaints are practical: parallel sessions use up plan limits much faster, one user reporting that a weekly limit can go in five hours, Windows is seen as behind the Mac version, and people want sessions grouped into workspaces by project.

What it means for you

1. Every session draws on your plan limit. Four sessions running at once use your plan about four times as fast as one. Run in parallel only the work that can't wait.
2. Split by files, not by topic. Two sessions that touch the same file will overwrite each other. Give each one separate folders, or turn on a worktree per folder in the environment.
3. Decide what comes back. A nested session reports into your main thread, so tell it what a useful report looks like before it starts. A five-line result is easy to act on; a full log is not.
4. Park quick questions with /btw. A "what does this flag do" belongs in that tab, so the long task keeps its context clean.

New to the app? Our guide to using Claude Code covers the basics, and the Claude Code cheat sheet lists the commands.

Try it

I want to run this job as parallel sessions. Split it into 2 to 4 tasks that never edit the same file. For each task give:
1) the goal in one line,
2) the files and folders it may change, and the ones it must not touch,
3) how we'll know it's done (a test, a command, a file that exists),
4) what to report back to this session, in no more than five lines.
If two tasks need the same file, merge them into one. Show me the split and wait for my go-ahead before starting any session.

The job: [describe the job and the repository].

Whenever you stop and wait for me in this session, end with a recap in this format:
- Done: what you finished, in one or two lines.
- Changed: the files you edited or created.
- Not done: what's left and why.
- I need from you: the one decision you're waiting on, with two or three options and the one you'd pick.
Keep it under ten lines and don't repeat earlier recaps.

Sources

• ClaudeDevs on X, announcement thread, October 14, 2026
• Claude Code Docs, Desktop application and desktop quickstart, checked October 15, 2026
• daily.dev, user reactions to the update, October 14–15, 2026