[GH-ISSUE #120] Copilot Ai not being detected #47

Closed
opened 2026-03-02 04:11:28 +03:00 by kerem · 3 comments
Owner

Originally created by @cWalsh-developer on GitHub (Oct 21, 2025).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/120

Originally assigned to: @svarlamov on GitHub.

In VS Code git-ai does not appear to recognise any code written by copilot or by the claude code extension.

  • Installed git-ai using WSL on Windows
  • Ran commits using both VS Code internal source control (https) and also via the CLI commands to test both ways of commiting
Image
Originally created by @cWalsh-developer on GitHub (Oct 21, 2025). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/120 Originally assigned to: @svarlamov on GitHub. In VS Code git-ai does not appear to recognise any code written by copilot or by the claude code extension. - Installed git-ai using WSL on Windows - Ran commits using both VS Code internal source control (https) and also via the CLI commands to test both ways of commiting <img width="1856" height="453" alt="Image" src="https://github.com/user-attachments/assets/66237306-a305-4bd7-a326-2d03c17c8e17" />
kerem 2026-03-02 04:11:28 +03:00
Author
Owner

@svarlamov commented on GitHub (Oct 22, 2025):

Thank you for the detailed report @cWalsh-developer! Will try to figure out what's going on here shortly!

Initially, I thought this was related to #83, but I think it's actually different since your git-ai is installed in WSL.

<!-- gh-comment-id:3430274191 --> @svarlamov commented on GitHub (Oct 22, 2025): Thank you for the detailed report @cWalsh-developer! Will try to figure out what's going on here shortly! Initially, I thought this was related to #83, but I think it's actually different since your `git-ai` is installed in WSL.
Author
Owner

@svarlamov commented on GitHub (Oct 22, 2025):

@cWalsh-developer Could I get your feedback on a few things? Please excuse my ignorance as my Windows experience is all pre-WSL

  1. How are you running Claude Code? https://docs.claude.com/en/docs/claude-code/setup#windows-setup -- is it via git bash or WSL?
  2. Are you running VS Code from WSL like this or is VS Code running entirely in native windows?
  3. From a Windows user perspective, what would the expected behavior be if git-ai is installed in WSL but VS Code is in native Windows? Would you expect it try to detect the installation from WSL and use that over the mount? I'm slightly concerned about that because I think the WSL git and Windows git work differently with regard to line endings etc. so I wouldn't want to introduce unexpected behavior.

Thanks in advance!

FYI If you're developing primarily in native Windows, I think the powershell-based installation is getting really close #123

<!-- gh-comment-id:3432494309 --> @svarlamov commented on GitHub (Oct 22, 2025): @cWalsh-developer Could I get your feedback on a few things? Please excuse my ignorance as my Windows experience is all pre-WSL 1. How are you running Claude Code? https://docs.claude.com/en/docs/claude-code/setup#windows-setup -- is it via git bash or WSL? 2. Are you running VS Code from WSL like [this](https://code.visualstudio.com/docs/remote/wsl) or is VS Code running entirely in native windows? 3. From a Windows user perspective, what would the expected behavior be if `git-ai` is installed in WSL but VS Code is in native Windows? Would you expect it try to detect the installation from WSL and use that over the mount? I'm slightly concerned about that because I think the WSL `git` and Windows `git` work differently with regard to line endings etc. so I wouldn't want to introduce unexpected behavior. Thanks in advance! FYI If you're developing primarily in native Windows, I think the powershell-based installation is getting really close #123
Author
Owner

@svarlamov commented on GitHub (Oct 23, 2025):

Lots of updates landed, so I think that this issue should be resolved now!

  1. Powershell installation is no longer experimental
  2. VS Code extension is fixed on Windows
  3. Installation will now configure git.path to point to git-ai because Windows VS Code doesn't actually look in the path before it looks in common installation dirs

To get the latest, please run the install script again and update git-ai for VS Code (should be automatically updated, but just to be sure).

If you need git-ai in both WSL and Windows, please install it in both environments (similar to how git is handled in WSL vs Windows). Would love to hear how it goes!

<!-- gh-comment-id:3437980653 --> @svarlamov commented on GitHub (Oct 23, 2025): Lots of updates landed, so I think that this issue should be resolved now! 1. Powershell installation is no longer experimental 2. VS Code extension is fixed on Windows 3. Installation will now configure `git.path` to point to `git-ai` because Windows VS Code doesn't actually look in the path before it looks in common installation dirs To get the latest, please run the install script again and update git-ai for VS Code (should be automatically updated, but just to be sure). If you need `git-ai` in both WSL and Windows, please install it in both environments (similar to how git is handled in WSL vs Windows). Would love to hear how it goes!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/git-ai#47
No description provided.