Made for the way you work
Isolated worktrees
Keep a focused change separate from the checkout you use for everything else.
In practice
A useful place to start
Start one task in a worktree while another chat works on a different branch. Each has its own files, and the final changes can be reviewed before integration.
Separate task files
A session worktree gives the task its own checkout and branch. File and shell tools use that location, helping keep unrelated local edits out of the task.
Make it a default
Use worktree mode for a single chat or make it the default for new sessions. Customize the branch prefix and setup guidance to match the project.
Track the cleanup
The worktree state stays visible in the session. Status and leave controls help you return to the original workspace and decide what to keep or remove.
Get started
Use the Worktree control in the chat, or enable worktrees for new sessions in Settings. Review the branch and changes before merging.
Good to know
Worktrees use disk space and need Git. They separate checkouts, not external services, databases, or all machine resources. Submodules and local setup may need project-specific steps.