[ENHANCEMENT] Git worktree management (enables parallel development workflows)

[hannesrudolph]

Type

Enhancement

Problem / Value

Users working on multiple features or bug fixes simultaneously need to switch branches frequently, which disrupts their workflow and loses context. Git worktrees allow working on multiple branches at once in separate directories, but managing them requires command-line knowledge and manual setup.

[roomote]

I'd like to help with this issue, but I need some clarification to ensure I implement the right solution. Could you please provide more details on the following:

1. Worktree Operations: Which git worktree operations should be supported?

   • Create new worktree (from existing branch or creating a new branch)?
   • List existing worktrees?
   • Remove/delete worktrees?
   • Switch between worktrees (open in a new VS Code window)?

2. Integration Approach: How should this integrate with Roo Code?

   • As a new dedicated tool (like execute_command, read_file, etc.) that the AI agent can use?
   • As slash commands (like /worktree create feature-branch)?
   • As a UI panel for manual worktree management?
   • All of the above?

3. Context Management: When switching to a different worktree:

   • Should Roo Code maintain separate task histories per worktree?
   • Should checkpoints be worktree-aware?
   • How should the current task context be handled when opening a worktree in a new window?

4. VS Code Integration: Should this leverage VS Code's multi-root workspace feature, or should each worktree open in a separate VS Code window?

5. Scope: Is there a minimum viable feature set you'd like to see first? For example, starting with just "create worktree and open in new window" functionality?

Please tag @roomote in your response with the answers, and I'll be happy to propose an implementation plan once I have this information.