[Bug]: Externally created Git worktrees are treated as “Local”
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
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
Workaround
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
Start in apps/desktop by reproducing the issue with a worktree created outside T3 Code, then trace how the application identifies the current repository folder. Compare the externally created worktree with one created through the app. Done means the T3 Code indicator identifies it as a Worktree and the Open button opens that worktree rather than the original repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100