[BUG] JetBrains plugin (0.1.14-beta): /ide selection succeeds silently but never establishes connection in WSL2 (PhpStorm running inside WSL2)

Open 💬 0 comments Opened Jul 15, 2026 by st9-spin

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?

Environment:

  • Claude Code CLI: v2.1.210 (native install)
  • JetBrains plugin: com.anthropic.code.plugin 0.1.14-beta
  • IDE: PhpStorm 2026.1.4 (Build #PS-261.26222.71), running natively inside WSL2 (not Windows-native with \\wsl$ mount) — confirmed via runningInWindows: false in lock file
  • WSL: Ubuntu 24.04.4 LTS, WSL2
  • Host OS: Windows 11
  • .wslconfig: networkingMode=mirrored already set (ruled out NAT/firewall cause)

What's wrong?
After restarting both WSL and PhpStorm completely, the plugin's integrated terminal is unable to auto-launch claude. Starting claude manually and running /ide shows the IDE as found but with a path-mismatch warning, even though the workspace path matches exactly:

Found 1 other running IDE(s). However, their
workspace/project directories do not match the
current cwd.
   ● PhpStorm: <project-path>

Verified exact match between pwd, realpath, and the lock file's workspaceFolders (byte-for-byte, checked with cat -A, no trailing whitespace/symlink differences):

{"workspaceFolders":["/home/<user>/<project-path>"],"pid":780,"ideName":"PhpStorm","transport":"ws","runningInWindows":false,...}

Selecting the entry (via mouse click or Enter) causes the PhpStorm window to flash briefly, then returns to the same selection screen without connecting. Pressing Esc shows "IDE selection cancelled." Repeating /ide shows the identical state every time.

Debug logs show nothing relevant:

  • claude --debug produces a debug log file, but it contains no lines related to the IDE connection attempt at the time /ide is used (checked around the exact timestamp).
  • claude --debug mcp shows MCP server activity (e.g. claude.ai Google Drive) but no log entries whatsoever for the internal ide MCP server, even immediately after attempting the /ide selection.

This suggests the selection UI is not actually triggering a connection attempt server-side, or the resulting attempt is not logged.

Additional notes:

  • Previously (before an update — exact version not tracked), the plugin auto-connected without needing manual /ide selection at all.
  • Only one PhpStorm project window / one lock file exists, ruling out the duplicate-entry issue from #54048.

What Should Happen?

Expected behavior:
/ide should connect automatically (or at minimum, on manual selection) when the workspace path matches exactly, and any connection attempt/failure should appear in debug logs.

Error Messages/Logs

Steps to Reproduce

  1. Ensure PhpStorm is running natively inside WSL2 (not via a Windows-native process on a \\wsl$ mount) and .wslconfig has networkingMode=mirrored set.
  2. Open a WSL2 terminal, cd into the project directory (e.g. /home/<user>/<project-path>).
  3. Launch PhpStorm from that directory and open the project.
  4. Fully quit both WSL2 (wsl --shutdown) and PhpStorm, then restart WSL2 and PhpStorm again.
  5. Open the integrated terminal inside the Claude Code plugin's tool window in PhpStorm.

→ Expected: claude auto-launches and auto-connects to the IDE.
→ Actual: the plugin does not auto-launch claude at all.

  1. In the same WSL2 terminal (or the plugin's terminal), manually start claude.
  2. Run /ide.

→ The picker shows the running PhpStorm instance, but with the warning: "However, their workspace/project directories do not match the current cwd."

  1. Confirm that pwd in the terminal exactly matches workspaceFolders in ~/.claude/ide/*.lock (verified byte-for-byte with cat -A, and with realpath to rule out symlinks).
  2. Select the PhpStorm entry in the /ide picker (via mouse click or Enter).

→ The PhpStorm window briefly flashes/refocuses, then the picker returns to the same unconnected state. No connection is established.

  1. Run /ide again → identical state is shown every time.
  2. Run claude --debug and claude --debug mcp while repeating steps 6–9.

→ No log entries related to the ide MCP server or the connection attempt appear in the debug log, even at the exact timestamp of the selection attempt.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.210

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_

View original on GitHub ↗