worktree and branch names are meaningless and difficult to work with. #4902

Copilot creates Git worktrees using random, non‑descriptive names, and this causes real workflow problems when using IntelliJ. When a worktree is created with a name that does not reflect its purpose. IntelliJ displays the project using the worktree folder name, so I end up with multiple open projects that look like random strings. When I return to those windows later, I cannot tell what work I was doing or what feature or fix the worktree was meant to represent.

There is no simple way to understand the purpose of these autogenerated worktrees once they appear in IntelliJ. The names provide no context, and IntelliJ does not show any additional clues. This makes navigation harder, slows down project switching, and creates confusion when trying to clean up old worktrees.

It would be much more helpful if Copilot generated worktree and branch names that reflect something meaningful, such as the file being edited, the feature being worked on, or a short description of the change. Clear names would make Copilot‑created worktrees easier to understand and manage across tools like IntelliJ.