[BUG] Claude Code IDE Connection Issue

Resolved 💬 28 comments Opened May 29, 2025 by AnrokX Closed May 29, 2025
💡 Likely answer: A maintainer (hackyon-anthropic, collaborator) responded on this thread — see the highlighted reply below.

Claude Code IDE Connection Issue

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.4
  • Operating System: WSL2 Ubuntu (Linux Legion 5.15.167.4-microsoft-standard-WSL2)
  • Terminal: zsh in WSL2

Bug Description

Claude Code CLI fails to detect IDE connections despite extensions being properly installed and accessible through Command Palette. The CLI consistently shows "No available IDEs detected" even when IDEs are running with Claude Code extensions installed and functional.

Steps to Reproduce

  1. Install Claude Code extension in IDE (tested with Cursor and Windsurf)
  2. Open project in WSL2 environment
  3. Verify extension is installed and Claude Code commands appear in Command Palette (Ctrl+Shift+P)
  4. Run claude command in WSL terminal from project directory
  5. Observe "No available IDEs detected" message in Claude interface
  6. Try running Claude Code commands from IDE Command Palette
  7. Check Claude terminal - no connection established

Expected Behavior

  • Claude Code CLI should detect running IDEs with Claude Code extension installed
  • IDE should appear in "Select IDE" menu in Claude terminal interface
  • Connection should be established allowing integrated development features

Actual Behavior

  • Claude Code CLI shows "No available IDEs detected" despite extensions being properly installed
  • Claude Code commands are visible and accessible in IDE Command Palette
  • No connection is ever established between CLI and IDE extension
  • Lock files in ~/.claude/ide/ show connection attempts but CLI doesn't recognize them

Additional Context

Lock File Evidence (before clearing):

{"pid":5467,"workspaceFolders":["/home/anrokx/Codebase"],"ideName":"Cursor","transport":"ws"}
{"pid":3078,"workspaceFolders":["/home/anrokx/Codebase"],"ideName":"Windsurf","transport":"ws"}

Troubleshooting Attempted:

  • Verified extensions installed and enabled in both Cursor and Windsurf
  • Cleared IDE lock files (~/.claude/ide/*.lock)
  • Killed and restarted all Claude processes
  • Restarted IDEs and WSL connections
  • Tested with single IDE to avoid conflicts
  • Confirmed IDE processes running with extension hosts
  • Tried initiating connection from both CLI and IDE sides

IDE Process Verification:

  • Cursor: cursor-server processes active with extension host
  • Windsurf: windsurf-server processes active with extension host
  • Multiple forwarded ports (15045, 30271, etc.) showing IDE services running

Command Palette Confirmation:
Claude Code commands visible and accessible:

  • "Claude Code: Insert At-Mentioned" (Ctrl+Alt+K)
  • "Fix with Claude Code"
  • Other Claude Code integration commands

The connection mechanism appears to work partially (lock files created with correct data), but the CLI fails to detect or communicate with the IDE extensions in WSL2 environment.

View original on GitHub ↗

28 Comments

MINTY1st · 1 year ago

I was just about to create an issue.
I'm in the same situation.
In my case, after I ran /ide and selected something like "none" under "cursor", I was unable to select "cursor" again.
The none option is fine, but I wish it was possible to select it again after selecting it.

!Image

The extension itself is installed.

!Image

I'm not good at English, so I'm using a translation site to write this.
Thank you.

opus131 · 1 year ago

Fantastic writeup @AnrokX!
I have the exact same issue with and cursor vscode in WSL2

jonzinho · 1 year ago

Hello guys, I have the exact same issue running Cursor in WSL2. Thank you for reporting it too @AnrokX, I thought it was happening only with me.

mrcodechef · 1 year ago

Same issue with vscode and vscode-insiders with WSL2 Ubuntu 24.04

 Claude Code Status v1.0.5

 Working Directory 
  L /home/xxx/src/xxx

 IDE Integration • /config
 ✔  Installed VS Code extension

 Account • /login
  L Login Method: API Key (/login managed key)
  L Email: xxx@xxxx

 Memory • /memory
  L project: CLAUDE.md

 Model • /model
  L Default (claude-sonnet-4-20250514)
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. 
AlanAltonchi · 1 year ago

Same problem in Cursor

hackyon-anthropic collaborator · 1 year ago

Thanks for the report, and sorry for the inconvenience! We have found the issue and submitted a fix, should be available in the next release!

younes-io · 1 year ago

!Image

It's fixed in the new version 1.0.6 !! Thank you!!

AnrokX · 1 year ago

IDE integration working properly now

Izverg1 · 1 year ago

i've been getting 'IDE disconnected' today , latest VSCode, on Windows 11, WSL Ubuntu , ARM64 .

elle-empower · 1 year ago

Also getting this for VSCode today on MacOS 14.7.4, M1 Pro chip

AustEcon · 1 year ago

Still getting the issue with latest claude code where it doesn't list the Rider IDE or gets disconnected. I have seen it work previously and it shows the diffs in the IDE but for some reason I haven't been able to get it to connect for the past week.

  • Windows 11, WSL Ubuntu , ARM64
AustEcon · 1 year ago

I figured out that if I use an external terminal (non-Rider integrated terminal) I can get it to work but I still need to close Rider and re-open it after entering a claude code session.

So it seems like there is some necessary event happening when Rider IDE initially loads the project to allow claude code to reach it... But claude code needs to be already in an active session to capture this event.

ariel-rahmane · 11 months ago

I'm also getting this issue

viktordanko · 11 months ago

+1 same here

VSCode

Version: 1.102.3
Commit: 488a1f239235055e34e673291fb8d8c810886f81
Date: 2025-07-29T03:00:23.339Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Darwin arm64 24.5.0
docbobo · 11 months ago

+1 (VSCode)

dmaass01 · 11 months ago

+1 (Cursor Version: 1.3.6)

CREAITIVE-THINKING · 11 months ago

Happening to me Cursor 1.3.5

khuyentran1401 · 11 months ago

Happening in Cursor 1.2.4

garyfpga · 11 months ago

happening in Cursor 1.2.2 and 1.2.4

ofaws · 11 months ago

happens to me after the latest Claude Code update in VS Code 1.102.3

Seems to be constantly disconnecting if I have another VS Code window opened (with other project), even if that other window DOES NOT use Claude Code

psilooo · 11 months ago

+1 vscode today after updating... so frustrating

hackyon-anthropic collaborator · 11 months ago

Thanks for the reports, we're investigating immediately!

tycerch · 11 months ago

WSL VSCODE IDE disconnect

I had another vscode window open for awhile (not running claude code) then I started noticing the IDE disconnect. I closed the second window and restarted my machine several times and still can't keep claude code connected to the IDE in a single window any longer, even after running /ide. Currently trying to reinstall claude code to see if that fixes things.

andrujuanoo · 11 months ago

+1 vscode

entrptaher · 11 months ago

Had this issue on my windows/wsl, vscode after updating, it still works fine on my mac where I didn't update the claude yesterday.

hackyon-anthropic collaborator · 11 months ago

This is likely a new issue with recent updates. We're investigating right now, but please comment/provide any additional information on this issue instead:
https://github.com/anthropics/claude-code/issues/4871

Thanks!

github-actions[bot] · 11 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.