Escriu per cercar…

Multiple

Working on multiple development streams with Claude depends on your workflow. If you are coding in terminal workspaces with Claude Code, you can manage parallel sessions, divide work among multiple AI agents, or split tasks across different folders

Aquesta pàgina encara no s'ha traduït — es mostra en l'idioma original:English

When you have more than one thing in flight — a feature, a bug fix, a review — you don’t have to finish them one at a time. The Claude Code CLI gives you three ways to run work in parallel. They differ in how isolated the streams are: from sharing a single conversation to running in completely separate folders. Pick by how much the streams need to stay apart.

PatternWhat runs in parallelIsolation
SubagentsSeveral agents inside one sessionShared files, shared chat
Multiple sessionsSeveral claude processes, one checkoutShared files, separate chats
Git worktreesSeveral claude processes, separate checkoutsFully isolated

Many agents, one session

The lightest option: stay in a single claude session and let it delegate independent jobs to subagents. Each subagent runs with its own context window and reports back a short summary, so the work happens in parallel without flooding your main conversation.

> Investigate three things in parallel: one subagent maps the auth
  flow, one lists every TODO/FIXME, and one checks test coverage.

Claude launches the subagents together and aggregates their answers. This shines for independent, mostly read-only jobs — search, audits, research — where you want one tidy result.

You can also define reusable agents in .claude/agents/ and manage them with the /agents command, so a dedicated “reviewer” or “test-runner” is one prompt away.

Background tasks

For a single slow job you don’t want to wait on, run it in the background and keep working:

> Run the full test suite in the background while we refactor the
  auth module.

Claude keeps the main session responsive and notifies you when the job finishes. Use /bashes to see what’s still running.

Multiple sessions, one folder

The quickest way to truly parallelize is to open another terminal tab and start claude again. Each session keeps its own context and history.

shell
# Terminal 1
claude

# Terminal 2 — same repository
claude

You rarely start from scratch. To pick up where you left off:

shell
claude -c          # continue the most recent session
claude --resume    # choose a past session from a list

Estàs llegint una vista prèvia.

Inicia sessió per llegir l'article complet. Qualsevol compte obre 4 articles gratuïts al mes; l'alumnat i el professorat llegeixen les pàgines del seu curs sense límit.

Inicia sessió