[BUG] JetBrains IDE integration failing after upgrading to v1.0.29
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other:
- Claude CLI version:
1.0.29 (Claude Code) - Operating System:
macOS 15.5 - Terminal: JetBrains IntelliJ IDEA Plugin -
Claude Code [Beta] 0.1.9-beta
Bug Description
After updating claude from 1.0.24 to 1.0.29, the claude process fails to integrate with the Claude Code IDE plugin (in JetBrains IntelliJ IDEA).
Steps to Reproduce
- Update
claudeto the latest1.0.29version viaclaude update - Try using it via the JetBrains IDE integration
Expected Behavior
Expect the Claude Code [Beta] 0.1.9-beta plugin to successfully connect to the claude process.
Actual Behavior
The claude status states that:
Installed IntelliJ IDEA plugin but connection is not established.
Additional Context
This IDE integration was working just fine until I updatedclaude.
I have tried numerous troubleshooting steps, including:
- restarting the IDE
- checking the
$PATH - removing and reinstalling the
Claude Code [Beta] 0.1.9-betaIntelliJ IDEA plugin
Note: In case it makes any difference, in my case I am using asdf to manage my NodeJS version, so claude is using a shim at ~/.asdf/shims/claude
Same issue for VSCode/Cursor
It looks like 1.0.27 is the last version that is able to connect to PyCharm for me, as 1.0.30 is still broken. I'm on the same OS version and plugin version. When I run the /ide command the message I get is "No available IDEs detected."
Rolling back to 1.0.27 makes it work right away without having to restart my IDE, so I've used claude config set -g autoUpdaterStatus disabled for now to keep it from auto-upgrading to the broken version.
Related issue: #2299
This is now resolved in the latest Claude Code (v1.0.35) and plugin (0.1.11-beta) versions.
This is now resolved in the latest Claude Code (
v1.0.35) and plugin (0.1.11-beta) versions.
I guess we still need to migrate the various JSONL and other files from the old .claude location to the new one?
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.