[Desktop] Display current worktree/cwd name in app UI (statusLine equivalent)

Any updates on this? Agree it's pretty painful not knowing which worktree I'm in consistently

I'm also curious about this. I'd like to switch to the APP, but no status bar is a real deal-breaker for my workflow.

Any updates on this?

This would genuinely be useful to have. Sorry to bring Codex App into this, but it offers this feature and it makes the workflow noticeably smoother.

This is really inconvenient. Are there no updates? It is difficult to find worktrees that I don't use every time.

Windows data point, plus: the stale indicator cannot be corrected, because the manual directory switch is rejected as a no-op

Adding a Windows occurrence (this issue is labelled platform:macos) and one behaviour I could not
find in any of the existing reports: the stale indicator is not just cosmetic, it is
uncorrectable from the UI.

Environment

• Claude Code 2.1.179, desktop app on Windows 11 Enterprise 10.0.26200
• git 2.52.0.windows.1

What happens

1. Session opens in C:\repo on branch A. Chip shows repo / A.
2. A worktree is created outside .claude/worktrees/:

git worktree add ..\repo-wt -b branch-B

1. EnterWorktree with path: C:\repo-wt. The move is real and verified:

• Get-Location → C:\repo-wt
• git rev-parse --abbrev-ref HEAD → branch-B
• git -C C:\repo rev-parse --abbrev-ref HEAD → still A (launch dir untouched, as intended)

1. Chip still shows repo / A, with a diff count for A. This part matches #46574 and #57251.
2. The new part: changing the directory manually to C:\repo-wt via the app fails with

"The session is already in this directory", and the chip still does not update.

Why step 5 matters

That error is correct about the real cwd — which is precisely the problem. The app's cwd state is
right, the chip is rendering the launch directory, and the no-op guard compares against the real cwd.
So the two disagree, and the guard blocks the only user action that would resync the display. The
session stays visually wrong for its whole life, with no recourse.

This reads as an internal inconsistency rather than a missing feature, so I think it survives #47159
being closed as not planned: even if the chip is never made to follow EnterWorktree
automatically, the manual switch should not be refused while the display disagrees with the cwd.

Impact

• Anyone reading along trusts the chip. In my case it advertised a feature branch with a

~35,000-line diff while the real work was a 4-file change on a different branch.

• The Commit changes button sits beside that stale label, and it is unclear which directory it

acts on — so it becomes unusable-by-caution for the rest of the session.

• Net effect: worktrees are the recommended way to stop concurrent sessions clobbering a shared

checkout, but using them makes the UI untrustworthy.

Notes for whoever picks this up

• Presentation-only: cwd, branch resolution, git commands and the EnterWorktree result were all

correct throughout.

• The indicator looks bound to the session's launch/project root rather than its live cwd.

#45202 (the VS Code button opening the original directory) looks like the same binding on another
surface.

• The settings schema lists a CwdChanged hook event, so the transition appears observable already —

the chip may just not be subscribed.

• Unverified: whether worktrees created by EnterWorktree (under .claude/worktrees/) behave

differently from an existing worktree adopted via path, as here. This report is the adopted-path
case only.

Workaround

ExitWorktree with action: "keep" returns the session to the launch directory, after which manual
directory changes are accepted again. For a correct chip from the start, launch the session with the
worktree as its directory instead of switching into one mid-session.

Prior reports (so this is not re-triaged as another duplicate)

• #46574 — desktop UI shows main's branch after EnterWorktree (closed, duplicate)
• #57251 — EnterWorktree succeeds, UI never switches (closed, duplicate)
• #47159 — request to update the branch display mid-session (closed, not planned)
• #60741 — desktop worktree awareness (closed, duplicate)
• #45202 — VS Code button opens the original directory