Here's the updated feedback message with concrete examples from my machine:

Here's the updated feedback message with concrete examples from my machine:

---

**Subject:** Inconsistent/random worktree naming and location — no way to configure

**Feedback:**

When the app creates a new git worktree for a session, the folder name and base location aren't consistent or configurable, and don't stay in sync with the branch name.

**Examples from my machine (project: connect-v2):**

Good — some sessions already land here, which is what I want for *all* of them:
```
/Users/dualeoo/WebstormProjects/connect-v2.worktrees/FUSE-16794-rais-404-fix-csharp-cleanup
/Users/dualeoo/WebstormProjects/connect-v2.worktrees/FUSE-16938-fix-rais-sso-slack-alert-routing-and-noise
```

Bad — other sessions for the *same project* land in a completely different root, with meaningless names:
```
/Users/dualeoo/WebstormProjects/copilot-worktrees/connect-v2/dualeoo-symmetrical-dollop
/Users/dualeoo/WebstormProjects/copilot-worktrees/connect-v2/dualeoo-urban-umbrella
```

**The folder name/branch mismatch:**
`dualeoo-urban-umbrella` currently has branch `FUSE-16919-rais-jwt-missing-token-logging` checked out — the branch got a meaningful name, but the folder never updated:
```
$ git worktree list
/Users/dualeoo/WebstormProjects/copilot-worktrees/connect-v2/dualeoo-urban-umbrella 27914cd89f [FUSE-16919-rais-jwt-missing-token-logging]
```
This shows the folder name/location is locked in at worktree creation time and never re-synced, even after the agent renames the branch to something meaningful.

**Request:**
1. Add a setting (global and/or per-project) to force the worktree base directory — e.g., always use `.worktrees/` as a sibling folder, matching the good examples above, instead of falling back to `~//copilot-worktrees//`.
2. Derive the initial worktree folder name from the branch name/task (e.g. ticket ID) instead of a random adjective-noun generator (`dualeoo-symmetrical-dollop`, `dualeoo-urban-umbrella`).
3. If the branch is renamed later in the session, rename/re-sync the folder too (or add an explicit "rename workspace folder" action), so folder and branch names never diverge like `dualeoo-urban-umbrella` vs `FUSE-16919-rais-jwt-missing-token-logging`.

This would make it much easier to track and navigate multiple parallel sessions on disk, especially with several active worktrees for the same repo.

---

Ready to paste into the feedback form. Let me know if you want it trimmed shorter or split into separate items.

---
| Field | Value |
| --- | --- |
| App version | 1.1.10 |
| OS | macOS 26.5.0 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 4 (Week 1) |

No files or tests are named. Start by tracing the app's worktree creation and branch-renaming entry points, then determine how base paths and folder names are selected. Done means configurable worktree placement, meaningful initial names, and folder resynchronization after branch renames, with coverage for each behavior.

索引モデルが issue の本文から書いたものです。