Repository navigation
[Bug]: Externally created Git worktrees are treated as “Local” #1714
Description
Activity
I encontered this too. In the session I pointed it to the correct directory, and I hope it will go well from there.
+1, this also breaks trust in the footer indicator more generally. Concrete case: the agent created a worktree + branch
feat/age-permis-conditionsfromorigin/devmid-thread, and the composer footer still shows "Local checkout · dev" for the rest of the conversation. As a user I can never tell with certainty which branch/worktree the thread is actually operating on — the indicator looks authoritative but reflects the initial binding, not reality. Looking forward to #3754.- added a commit that references this issue
on Sep 14, 2026 - added a commit that references this issue
on Sep 17, 2026
Before submitting
Area
apps/desktop
Steps to reproduce
create a new thread;
ask the model to create a new worktree (or have it on AGENTS.md as steps to start a new task like I do)
check T3 Code indicator pointing as "local"
check the "Open button" loading the original repo folder, instead of the worktree.
Expected behavior
The worktree should be recognized as a Worktree, regardless of how it was created
Actual behavior
T3 Code does not recognize the new Worktree and it thinks it's on the original repo folder.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
ss.png
Workaround
No response