[BUG] IDE integration broken after auto-update from v1.0.27 to v1.0.28+
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other:
- Claude CLI version: v1.0.28+ (issue occurs), v1.0.27 (works correctly)
- Operating System: Ubuntu 22.04
- Terminal: Windows Terminal
Bug Description
IDE integration functionality stopped working after Claude Code's automatic update from v1.0.27 to v1.0.28 and later versions. While the extension installation message appears on startup, the usual "IDE connected" notification is missing, and the /ide command reports no available IDEs.
Steps to Reproduce
- Have Claude Code v1.0.27 working correctly with VS Code integration
- Allow automatic update to v1.0.28 or later version
- Start Claude Code
- Observe that extension installation message appears but "IDE connected" message does not
- Run
/idecommand - Notice that no candidate IDEs are found/displayed
Expected Behavior
- "IDE connected" message should appear on startup when VS Code is detected
/idecommand should list VS Code as an available IDE option- IDE integration should work as it did in v1.0.27
Actual Behavior
- Extension installation message appears on startup
- "IDE connected" message does not appear
/idecommand reports no available IDEs- IDE integration functionality is non-functional
Additional Context
Workaround: The issue can be temporarily resolved by:
- Downgrading to v1.0.27:
npm install -g @anthropic-ai/[email protected] - Disabling auto-updates:
claude config set -g autoUpdaterStatus disabled
This suggests the regression was introduced in v1.0.28 and affects the IDE detection/connection mechanism specifically.
@akineko thank you very much for the workaround🙏. I spent an hour dealing with this issue 🙄.
I found a possible issue on Linux. Claude Code started using ~/.config/claude instead of ~/.claude. When I create a symlink with ln -s ~/.config/claude ~/.claude, the IDE works for me.
EDIT:
This is not an official solution — you do it at your own risk. You must stop all running instances of Claude before making changes. Rename the ~/.claude directory, and copy any missing files from it into ~/.config/claude. Only then create the symlink.
I don't know how Anthropic will handle this in the future — they might try to unify the config paths, and the symlink could cause issues or even lead to data loss. Make sure to back up your configs regularly.
Thanks @orgoj, your comment pointed me in the right direction for MacOS as well. I just copied ~/.claude/ide into ~/.config/claude/ and that made the IDE integration work again, also with the latest 1.0.31. After that I created the same symlink that you created. Fwiw, my IDE is PyCharm.
The current situation in my machine (macOS) is, to put it mildly, a mess:
The ide folder in ~/.claude was updated today while I was using Claude Code.
The folder ~/.config/claude contains a few files, but not exactly everything that is in ~/.claude. It's missing settings.json and my global CLAUDE.md.
I didn't do a deep recursive comparison between the two folders -- only a quick top-level check.
Looks like something might've gone wrong when someone was trying to fix https://github.com/anthropics/claude-code/issues/1455. Maybe just a partial fix caused a mess and/or lack of a migration script from ~/.claude to ~/.config/claude might've made things worst.
Potentially they didn't sync well the change of configuration folder between Claude Code and the VSCode extension.
Good to know about this -- The config directory change probably also has something to do with my issue #2333
Thank you all for the investigation- it is indeed a config dir difference between the two, specifically when XDG_CONFIG_HOME is specified and you run claude.
I fixed it with rm -rf ~/.config/claude && ln -s ~/.claude ~/.config/claude. (This is the opposite operation of ln -s ~/.config/claude ~/.claude introduced by orgoj.)
However, when the corrected version is created, I think the two folders will be integrated or migrated, so please be aware that there is a possibility that some kind of problem may occur, and proceed at your own risk.
FYI there's already Claude Code and VSCode extension v1.0.31, which fixed everything. I can confirm that by default they are both using ~/.config/claude.
Claude Code and VSCode extension v1.0.31, which fixed everything.
still broken on Jetbrains
I can confirm that in Cursor the extension writes the lock file in the ~/.claude/ide directory, while claude cli expects it under ~/.config/claude/ide directory.
Creating a symlink of ~/.claude/ide under ~/.config/claude dir fixes the issue. (ln -sfn ~/.claude/ide ~/.config/claude/ide)
The extension must be updated to write the lock file in the new config dir.
I can confirm that in Cursor the extension writes the lock file in the ~/.claude/ide directory, while claude cli expects it under ~/.config/claude/ide directory. Creating a symlink of ~/.claude/ide under ~/.config/claude dir fixes the issue. (
ln -sfn ~/.claude/ide ~/.config/claude/ide) The extension must be updated to write the lock file in the new config dir.
That is the same case for the JetBrains plugin.
So I'm left with a mess where I can't resume previous sessions as they didn't get migrated to the new folder structure. #2302
Are we supposed to move files over manually? Are there any instructions? Also Anthropic documentation still says the settings.json is in ~/.claude, no mention of $XDG_CONFIG_HOME:
https://docs.anthropic.com/en/docs/claude-code/settings#settings-files
So I'm left with a mess where I can't resume previous sessions as they didn't get migrated to the new folder structure. #2302
Are we supposed to move files over manually? Are there any instructions? Also Anthropic documentation still says the settings.json is in ~/.claude, no mention of $XDG_CONFIG_HOME:
https://docs.anthropic.com/en/docs/claude-code/settings#settings-files
Hi, I've just migrated manually from .claude directory to ./config/claude one, everything works fine (I'm on 1.0.31). Plus see my comment above on symlinking the ide directory.
Just pay attention to:
- exit every CC instance
- migrate files inside directories, so that you'll merge old data into newer one
- do not overwrite lock files and other state files (you need to apply some heuristics here, but it's doable)
Update: I tested with version 1.0.34 and the issue has been resolved! 🎉
The IDE integration is now working correctly again. Thank you to the Claude Code team for fixing this, and also thanks to everyone who shared additional information and helped troubleshoot this issue.
Since the problem is resolved, I'm closing this issue.
Thanks for the report and all the sleuthing to track this down - it's indeed fixed. We recommend removing the symlink if you made one.
@igorkofman removed symlink
~
❯ ls -l .claude
lrwxr-xr-x 1 tkaovila staff 15 Jun 23 17:14 .claude -> .config/claude/
~
❯ rm .claude
~
❯ ls -l .claude.json
-rw-r--r--@ 1 tkaovila staff 126595 Jun 25 08:54 .claude.json
~
❯ claude
/Users/tkaovila/.config/claude/local/claude: line 2: /Users/tkaovila/.claude/local/node_modules/.bin/claude: No such file or directory
/Users/tkaovila/.config/claude/local/claude: line 2: exec: /Users/tkaovila/.claude/local/node_modules/.bin/claude: cannot execute: No such file or directory
Think it's still referring back there... will have to edit some files
~ 8s
❯ cat $XDG_CONFIG_HOME/claude/local/claude
#!/bin/bash
exec "$XDG_CONFIG_HOME/claude/local/node_modules/.bin/claude" "$@"
Updating to this fixed it.
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.