Codex Desktop “Pinned summary” shows another task’s worktree and branch after creating tasks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.61601
What subscription do you have?
Pro 5x
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
After creating a new worktree-backed task or a new chat/task in Codex Desktop, the “Pinned summary” of other existing tasks can show the local/worktree environment and branch belonging to a different task.
The actual Git worktree state does not appear to be corrupted:
- Each affected task terminal continues to operate in its correct worktree.
pwd,git branch --show-current, andgit worktree listreport the expected task-specific path and branch.- The mismatch appears limited to the worktree/branch information displayed in “Pinned summary”.
Quitting and reopening Codex Desktop restores the correct worktree and branch display for the affected tasks.
This looks like stale or cross-task UI state being reused after task or worktree creation, rather than an actual Git worktree mix-up.
What steps can reproduce the bug?
- Open a local Git repository in Codex Desktop.
- Create or open Task A backed by worktree/branch A.
- Create a new worktree-backed Task B, or create another new chat/task for the same repository.
- Return to Task A and inspect its “Pinned summary”.
- Observe that the displayed local/worktree environment or branch can belong to Task B, or vice versa.
- In the terminal of each task, run:
pwd
git branch --show-current
git worktree list
- Observe that the terminal and Git state remain correct for each task, despite the incorrect “Pinned summary” display.
- Quit and reopen Codex Desktop.
- Observe that “Pinned summary” now displays the correct local/worktree environment and branch again.
What is the expected behavior?
“Pinned summary” should always display the active task’s own local environment, worktree path, and branch.
Creating a new worktree-backed task or a new chat/task must not alter the displayed environment of other existing tasks.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Codex Desktop with two worktree-backed tasks and compare each task’s Pinned summary with pwd, git branch --show-current, and git worktree list. Trace the state used to render the summary after creating a task or chat, then verify that each task retains its own environment and branch without requiring an app restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100