Best practices for Claude Code changedbest-practices
Nearest release: v2.1.250, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−1removed
From line
458
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits24to this page, all time
The whole hunk
from line 458, old and new numbered
/
from line 458
458458 Run multiple Claude sessions in parallel to speed up development, run isolated experiments, or start complex workflows.
459459</Tip>
460460
461Pick the parallel approach that fits how much coordination you want to do yourself:
461Pick the parallel approach that fits how much coordination you want to do yourself, and add messaging when the sessions need to pass findings between them:
462462
463463* [Worktrees](/docs/en/worktrees): run separate CLI sessions in isolated git checkouts so edits don't collide
464* [Cross-session messaging](/docs/en/cross-session-messaging): let the sessions you run yourself pass findings to each other
464465* [Desktop app](/docs/en/desktop#work-in-parallel-with-sessions): manage multiple local sessions visually, each in its own worktree
465466* [Claude Code on the web](/docs/en/claude-code-on-the-web): run sessions in the cloud, on Anthropic-managed infrastructure by default
466467* [Agent view](/docs/en/agent-view): research preview. Run `claude agents` to dispatch sessions that keep running in the background and watch them from one screen
No line in this hunk matches that.