[BUG] /ide reports my JetBrains IDE, but misinterprets the path

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When I run /ide in Claude, it correctly identifies my running JetBrains IDE (GoLand 2025.3.3), but reports that "... their workspace/project directories do not match the current cwd".

❯ /ide

────────────────────────────────────────────────────────────────────────
  Select IDE
  Connect to an IDE for integrated development features.

  No available IDEs detected. Make sure your IDE has the Claude Code extension or plugin installed and is running.

  Found 1 other running IDE(s). However, their workspace/project directories do not match the current cwd.

     • GoLand: /mnt/c/projects/phosphor

  Enter to confirm · Esc to cancel

This is not correct; /ide is reporting the WSL path of my project, but GoLand is not running under WSL and does in fact have the project open at the same path as Claude. Both Claude and GoLand are running under Windows.

Speculation: is Claude misinterpreting the path reported by Git Bash (which it insists on using, even under Windows, to my eternal frustration) as a WSL path?

What Should Happen?

Claude should correctly identify the running IDE's and allow me to select them and connect.

Error Messages/Logs

Steps to Reproduce

On Windows, with WSL installed (but not being used).

1. Create a new Go project.
2. Open the project in JetBrains GoLand.
3. Open a PowerShell or command prompt, and start a claude session inside the Go project directory.
4. Type /ide in the Claude session

Expectation: you are able to connect Claude to the running GoLand instance.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_