Claude Code Desktop reportedly adds a hub for parallel sessions

• Claude Code Desktop has a hub for starting and tracking parallel sessions, demonstrated in testingcatalog's walkthrough.
• Saved environments reduce repeated setup, while nested tasks report back to the main conversation, according to WesRoth.
• Live session states, recap cards and task lists make concurrent work easier to follow; aibuilderclub_ also reports visibility into context usage and file changes.

The desktop reference also lets Claude check on, message and archive other sessions. Even suggested prompts consume usage: Anthropic says generating them requires a short background request that counts toward plan limits or API costs.

The refresh feels “almost like a v2” to trq212, with seven additions catalogued by daniel_mac8:

1. Saved environments: reuse a setup containing a few folders, an SSH host or a cloud environment.
2. Git worktrees: give parallel sessions separate working copies rather than overlapping edits in one checkout.
3. Nested sessions: ask Claude for parallel tasks, with each reporting results back to the main thread.
4. /btw: open a side question in its own tab with Cmd+; while the main session keeps working.
5. One-click follow-ups: launch Claude's suggested next task as a separate session.
6. Sidebar status: see which sessions are working and which need attention.
7. Recap cards and live to-do lists: catch up without rereading the full conversation.

The sidebar distinguishes sessions that are running, waiting for input or finished. Within a session, context usage and file changes provide additional visibility beyond task progress.

The attention queue is the best part of the refresh.

Desktop's worktree isolation is selected when starting a session, according to Anthropic's worktree documentation. Each worktree has its own files and branch, while sharing repository history and remotes.

A fresh checkout does not automatically reproduce the main checkout's development environment:

• Dependencies: installation and project setup happen in the new worktree.
• Ignored files: .worktreeinclude can carry files such as .env into newly created worktrees.

The documentation distinguishes three separate mechanics: worktrees isolate file edits, subagents split tasks within a session, and cross-session messaging passes findings between sessions.

Kanna can route every new project message to a thread marked “Delegator,” which dispatches work across harnesses, models and reasoning efforts, according to jakemor.

A Kanna delegator assigns a read-only investigation to a sub-chat

Firstmate uses one supervising agent with workers in visible terminal sessions, each assigned a clean worktree. Its README distinguishes two task shapes:

• Ship: authorized code changes.
• Scout: standalone investigation reports.

The project grew out of manually juggling sessions, kunchenguid wrote, with the aim of having the agent handle the context-switching.