[Bug]: T3 Code does not detect GitLab CLI installed via WinGet on Windows
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
Not sure
Steps to reproduce
- Install GitLab CLI on Windows using WinGet:
winget install glab.glab
- Verify that GitLab CLI is installed:
glab --version
- Restart T3 Code.
- Open a project hosted on GitLab.
- Try to use a GitLab-related feature or execute glab from the environment used by T3 Code.
Expected behavior
T3 Code should detect the installed glab executable and allow GitLab-related features to use GitLab CLI.
Actual behavior
T3 Code does not detect GitLab CLI and reports that glab is unavailable, even though it was installed using WinGet and is available from a regular Windows terminal.
Impact
Blocks work completely
Version or commit
No response
Environment
Windows 11
Logs or stack traces
Screenshots, recordings, or supporting files
No response
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
Reproduce the issue on Windows 11 by installing GitLab CLI with winget install glab.glab, then compare glab --version in a regular terminal with T3 Code's environment. Locate the executable-detection path for glab and verify that GitLab-related features recognize the installation afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100