[FEATURE] Better worktree names on Claude Desktop

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When checking the "Worktree" checkbox when creating a new session, right now claude creates a random name for the worktree, e.g. lucid-archimedes-aaaaa0.

1. This does not match the terminal version's --worktree <name> flag
2. Because of these random names, whenever I use external tools from that worktree, it becomes very difficult to identify which tab/window in that external tool matches which session, e.g.:

• my iTerm tab names are now lucid-archimedes-aaaaa0, recursing-maxwell-1b485f, musing-ramanujan-6e77cf
• my text editor window names are now lucid-archimedes-aaaaa0, recursing-maxwell-1b485f, musing-ramanujan-6e77cf
• my Fork (Git client) tabs are now lucid-archimedes-aaaaa0, recursing-maxwell-1b485f, musing-ramanujan-6e77cf

And just listing my worktrees with git worktree list gives me very little idea which worktrees are associated with which work.

This is impeding my ability to efficiently and safely work on features simultaneously in the same project, using my preferred tooling, and this will get worse over time and I get better at working on tasks concurrently.

Proposed Solution

• When checking the "worktree" checkbox, an input field should appear next to it, allowing you to specify a worktree name.
• It should be indicated somehow that this input is optional
• This input should probably be autofocused when toggling worktree on

This matches the behaviour of the terminal version of this feature, which allows you to specify a name as an argument to the --worktree flag like so:

claude --worktree my-feature-name

Alternative Solutions

Another option would be allow renaming of worktrees via a command, or via asking Claude. Claude currently tells me renaming the worktree isn't possible/advisable as the Claude session is rooted in the worktree, saying many things may break if it was renamed.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Additional Context

_No response_