Desktop UI shows 'main' branch instead of worktree branch after EnterWorktree

[burntcones]

Bug

After entering a git worktree via EnterWorktree, the Desktop app UI continues to display the main repo's branch (e.g., main) instead of the worktree's branch (e.g., claude/loving-torvalds).

Steps to Reproduce

1. Open Claude Code Desktop app in a git repo on main
2. Use EnterWorktree to enter/create a worktree (e.g., loving-torvalds)
3. Observe the branch indicator in the Desktop UI

Expected

UI shows the worktree branch: claude/loving-torvalds

Actual

UI still shows main (the branch of the original repo root).

Verification

CLI commands confirm the session is correctly operating in the worktree:

CWD: /Users/.../bc-retail-hub/.claude/worktrees/loving-torvalds
Branch: claude/loving-torvalds
Git dir: /Users/.../bc-retail-hub/.git/worktrees/loving-torvalds
Toplevel: /Users/.../bc-retail-hub/.claude/worktrees/loving-torvalds

All file operations and commits happen on the correct worktree branch — this is purely a UI display issue.

Environment

• Claude Code Desktop app (macOS)
• Darwin 25.3.0
• Git worktree created via .claude/worktrees/

[github-actions]

Found 3 possible duplicate issues:

1. Show active worktree branch in status bar instead of root repo branch #39848
2. Worktree/branch awareness: UI doesn't reflect active worktree or detect associated PRs #45881
3. PR not linked to session when working in a git worktree #44977

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #39848.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.