worktrunk

You can run parallel Claude Code agents by creating isolated Git worktrees for each task. This allows multiple features or experiments to be developed simultaneously without touching the main repository.

Managing Git worktrees involves using commands to create, switch, list, and merge isolated work environments. You can apply this workflow to develop multiple features simultaneously and auto-cleanup worktrees when merging back to the main branch.

Yes, you can use PR/MR checkout workflows to review changes in isolation. This creates a separate worktree for the pull request, allowing you to test and review branches without affecting your local working directory.

You can list current Git worktrees along with their status and CI-like context using the list command. This provides an overview of all active work environments and their current state within your project.

Yes, the worktree workflow integrates with project hooks for both setup and cleanup. This ensures that your isolated environments are properly configured when created and automatically removed when no longer needed.

You should avoid Git worktrees if your project does not use Git or if your development workflow requires all changes to be made directly in a single working directory without isolated environments.