Problem statement
It would be nice if when creating a new worktree, we could manually specify a name for it. Claude at least supports this with their worktree feature via claude --worktree my-worktree-name. Personally, I tend to find the "misty-morning" style random names to be confusing. It also means you need to make a new branch (or rename it) before creating a PR, if you want a more descriptive branch name in GitHub's merge commit message.
You can get around this by having an ongoing session in the main project folder (that you use to tell an AI to create worktrees for you, or could use the terminal feature and do it yourself if on the web). Then when you create your feature session, can select the existing worktree, but is all a bit more work. It has the advantage that you can make sure you've fetched the latest from git before basing on a particular branch, but you could also fix that easily after the session has been created (fast-forward the branch if needed).
Proposed solution
Just an an optional additional textbox to specify a name manually
Acceptance criteria
When text is put into the optional textbox, the resulting worktree and branch use that name instead of generating a random name.
Non-goals (optional)
No response
Priority (optional)
None
Additional context (optional)
No response
Problem statement
It would be nice if when creating a new worktree, we could manually specify a name for it. Claude at least supports this with their worktree feature via
claude --worktree my-worktree-name. Personally, I tend to find the "misty-morning" style random names to be confusing. It also means you need to make a new branch (or rename it) before creating a PR, if you want a more descriptive branch name in GitHub's merge commit message.You can get around this by having an ongoing session in the main project folder (that you use to tell an AI to create worktrees for you, or could use the terminal feature and do it yourself if on the web). Then when you create your feature session, can select the existing worktree, but is all a bit more work. It has the advantage that you can make sure you've fetched the latest from git before basing on a particular branch, but you could also fix that easily after the session has been created (fast-forward the branch if needed).
Proposed solution
Just an an optional additional textbox to specify a name manually
Acceptance criteria
When text is put into the optional textbox, the resulting worktree and branch use that name instead of generating a random name.
Non-goals (optional)
No response
Priority (optional)
None
Additional context (optional)
No response