Claude Code is no longer just a tool for one person. When you assign multiple tasks, Claude splits the work, delegates to other Claude instances, and reports back when finished.
Even while writing this article, I requested two research tasks. Two Claudes worked simultaneously and returned results on official information and competitor articles.
What Changed
A major update arrived for the Claude Code desktop app. The core improvement is easier management of parallel sessions.
In the new session screen, you can select execution locations like local, SSH, or cloud as "environments." Parallel tasks launch as child sessions and report results to the main conversation upon completion. However, reading feature lists doesn't clarify where to use them. Let's look at specific use cases.
Usage 1: Ask Claude to "Split" Tasks You Want to Run in Parallel
This is the heart of "running a team solo." When you assign unrelated tasks together, Claude launches child sessions for each. Results return to the main conversation as they finish.
One sentence is enough:
Proceed with these two tasks in separate sessions in parallel. Report results here when done. 1. Research official info on ○○ and summarize key points in 5 lines. 2. Check if similar articles exist and list up to 5.
I tested this while writing. I requested "checking official updates" and "checking for similar articles." Two sessions ran side-by-side on screen, and reports arrived in the main conversation. I only needed to read the delivered reports.
The main conversation stays clean with only reports. Sometimes Claude suggests moving a task to a separate session. Clicking the suggestion starts it as a new session.
Usage 2: Track Progress via To-Do List Below Messages
When you assign work, Claude's plan appears as a To-Do list below the message. While taking screenshots for this article, four items appeared from "test full-screen screenshot capability" to "insert into Typefully draft," checking off as completed.
You can see progress without reading long intermediate outputs. Just glance while doing other work.
Usage 3: Decide Next Steps via Summary Card Buttons
After a task finishes, a card summarizes what's done and what remains in 2-3 sentences. If you need to decide next steps, questions and buttons appear. This morning, options were "Fix in casual tone" or "Fix in polite tone" for "Create revised draft incorporating feedback?"
Click buttons instead of typing replies to proceed.
Usage 4: Off-Topic Questions Go to /btw
During work, you might wonder "What does this mean?" Typing /btw in the input field or pressing Cmd + ; on Mac opens a side chat. Official docs state this chat reads the main conversation but writes nothing back.
Resolve minor doubts without interrupting main work. Note: this chat disappears when closing the app. Save important answers elsewhere immediately.
Pitfall: Don't Let Two Sessions Edit the Same File
Parallelism tempts you to run everything simultaneously. But if two sessions edit the same file in the same folder, changes may overwrite each other.
For Git-managed folders, select "worktree" next to the branch name when starting sessions. Each session gets its own workspace, preventing conflicts. My two parallel tasks were both research-only. Only parallelize tasks with non-overlapping files.
Getting Started
On Mac, update via Menu > Claude > Check for Updates. On Windows, use Help > same option. Then start new sessions.
My Verdict
Start by parallelizing just two research tasks. Never begin by parallelizing file-editing work. Research has no conflict risk. As you gain experience, monitor progress via To-Dos and summary cards, then split tasks with non-overlapping files.
Running a team solo requires smart task division more than numerous Clauses.
If unsure where to integrate Claude Code in your workflow, I'll help organize suitable usage methods.
Free consultation:
