[BUG] Claude Code IDE connectivity issues with the latest update (1.0.64)

---

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/4837
2. https://github.com/anthropics/claude-code/issues/4854
3. https://github.com/anthropics/claude-code/issues/2554

If your issue is a duplicate, please close it and 👍 the existing issue instead.

🤖 Generated with Claude Code

---

OS: Mac OS Sequoia
Terminal: zsh
IDE + version: cursor 1.3.7
Claude CLI version: Claude Code v1.0.64

How long ago did this started happening?

Started this morning.

Steps to Reproduce

1. After it disconnects, I can reconnect using /ide.
2. It stays connected if I am asking questions.
3. It disconnects after it makes the first ide interaction - for example, after it displays the first diff view.

Same issue for me. Running Claude Code in verbose and debug mode, I see the following error message repeated (a lot):

[ERROR] MCP server "ide" Transport error: Error: Uncaught error in notification handler: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "params",
      "uri"
    ],
    "message": "Required"
  }
]

OS: Windows 11 Pro 24H2, Build 26100.4770
Terminal: Git Bash
IDE + version: Visual Studio Code 1.102.3
Claude CLI version: 1.0.64 (local installation, installed in Windows, not WSL)

Noticed this after updating to 1.0.64 yesterday.

1. /ide, select Visual Studio Code
2. Connects
3. When it begins to interact with the IDE, it disconnects. Example: I select a line and ask a question. It reads the line, but disconnects after it begins to answer.
4. Can reconnect with /ide, but cannot do so without interrupting or waiting for Claude Code to finish its current tasks.

Thanks for the reports! We have identified the issue and a fix is incoming ASAP!

Thanks for the swift triage and response!

OS: Mac OS Ventura
Terminal: zsh
IDE + version: Windsurf latest
Claude CLI version: Claude Code v1.0.64 (latest)

How long ago did this started happening?

just updated claude code like an hour ago, then it happened.

Steps to Reproduce

After it disconnects, I can reconnect using /ide.
It stays connected if I am asking questions.
It disconnects after it makes the first ide interaction - for example, after it displays the first diff view.

We've just released a new hotfix build (1.0.65), which should fix this issue:
https://www.npmjs.com/package/@anthropic-ai/claude-code/v/1.0.65

Please update when you get a chance, and let us know if you encounter any issues. Apologies for the inconvenience!

Solved here, thank you @hackyon-anthropic !

Operating System: Windows 10.0.26100 IDE: Cursor, version 1.5.11 Claude Code, version: 1.0.108 Terminal: PowerShell / Git Bash

Claude Code Extension Status: "Claude Code for VSCode" is installed and active in Cursor. Claude Code Extension Logs: "MCP Server running on port 61774 (localhost only)" Claude Code CLI Executable Location: C:\Users\<user>\.local\bin\claude.exe PATH Environment Variable: C:\Users\<user>\.local\bin is confirmed to be in your system PATH. Problem Description: claude /ide consistently returns "No available IDEs detected."

• Key Troubleshooting Steps Taken:
• Verified cursor command in PATH.
• Confirmed no custom CLAUDE_CONFIG_DIR.
• Successfully performed native Windows PowerShell installation of Claude Code.
• Verified claude.exe exists and is in PATH.
• Restarted shell and Cursor multiple times.

I keep having to run the /ide command or clicking into a file editor and back to the terminal in vscode insiders for claude code to see the active file

<img width="166" height="58" alt="Image" src="https://github.com/user-attachments/assets/8f55ddd1-ec04-4f6b-85ba-7f84d284a2f9" />

would be great to have the integration be more reliable

@marcospgp it's likely another issue. Can you file a new issue with info for repro? We will need some info on your setup/IDE/OS/version/repro steps

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

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.