[BUG] Windows IDE integration PHPstorm - No available IDEs detected.

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?

Claude Code fails to detect or connect to PhpStorm IDE in WSL2 environment. The IDE is not visible to Claude Code upon initial startup. Connection only succeeds after executing the /ide command repeatedly (sometimes 20+ times), after which PhpStorm suddenly appears and becomes available.

What Should Happen?

Claude Code should detect and connect to PhpStorm IDE reliably on first attempt or within the first few /ide command executions in a WSL2 environment.

Error Messages/Logs

No explicit error messages are shown. The /ide command simply returns without showing PhpStorm as an available IDE until after multiple attempts.

Steps to Reproduce

1. Environment setup:

• Windows 11 with WSL2 (Ubuntu distribution)
• PhpStorm installed and running on Windows host
• WSL2 networking mode: NAT (also tested with Mirrored mode - same issue)
• Windows Firewall rules configured to allow WSL2 traffic

1. Start PhpStorm on Windows host
2. In PHPstorm start the Claude code plugin or terminal and start:

claude

1. Execute the /ide command to list available IDEs
2. Observe that PhpStorm is not listed
3. Repeat step 4 multiple times (10-20+ executions)
4. Eventually, PhpStorm suddenly appears in the IDE list and connection succeeds

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.67

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

IntelliJ IDEA terminal

Additional Information

• WSL2 Network Configuration: Tested with both NAT mode (default) and Mirrored networking mode - issue persists in both configurations
• Firewall: Windows Firewall rules have been configured to allow WSL2 traffic, but this has not resolved the issue
• Workaround: Repeatedly executing /ide (10-20+ times) eventually results in successful detection, suggesting an intermittent connectivity or discovery issue rather than a complete blocking