[Bug]: Adding a new project from Gitlab with Open in Finder results in no clone
Open
Nobody has claimed this yet.
accepted
bug
via-triage
- 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
- Select existing repo from Gitlab
- Use the 'Open In Finder' button
- Select the location for the project
- Click Finders 'Open' button
Expected behavior
When clicking 'Open' the repo should be cloned the same as in app directory selection.
Actual behavior
The project will be added to T3 Code, but it won't clone the repo.
Impact
Minor bug or occasional failure
Version or commit
0.0.43-nightly.20260919.1978
Environment
MacOS Tahoe 26.6.2
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
Delete the project and re-add using T3 Codes in app directory selection
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 and trace the GitLab project flow from the “Open In Finder” button through the Finder location selection. Compare it with the app directory selection flow, then reproduce the issue on macOS and verify that choosing “Open” both adds the project and clones the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100