Cursor Blame fails in WSL because getGitFileLineBlame uses Windows-style path separators

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

WSL repo path: /home/joyj/projects/xxx/xxx
Git works in terminal and VS Code Git/GitLens can run blame successfully.

Cursor Blame fails:
getGitFileLineBlame failed for \home\joyj\projects\xxx\xxx\xxx\xxx\xxx\xxx\xxx.py
Failed to execute git

Expected:
Use /home/joyj/projects/xxx/xxx/xxx/xxx/xxx/xxx/xxx.py

Steps to Reproduce

  1. On Windows with WSL2, open a Git repository located inside the WSL filesystem, for example:
    /home/<user>/projects/<repo>

  2. Open the repository in Cursor using the Editor Window / WSL remote environment.

  3. Open any tracked file that has Git commit history.

  4. Right-click inside the file editor and select:
    Cursor Blame: Toggle File Blame

  5. Observe the Cursor Blame panel / popup.

Actual Behavior

Cursor Blame shows:

No blame data available for this file

In the Cursor Indexing & Retrieval output channel, the following warning appears:

getGitFileLineBlame failed for \home\<user>\projects\<repo>\path\to\file.py Failed to execute git

The file path is using Windows-style backslashes even though the workspace is running in WSL.

Expected Behavior

Cursor Blame should use the WSL/Linux path:

/home/<user>/projects/<repo>/path/to/file.py

and should be able to execute Git blame successfully.

Operating System

Windows 10/11

Version Information

Version: 3.8.23 (user setup)
VS Code Extension API: 1.105.1
Commit: 7cf19b7482706625cdb70db3211b7dd035b7aa30
Date: 2026-06-23T14:57:42.334Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @joyj

Thanks for a great bug report. I can reproduce this exactly as you described. Filing with the team.