[BUG] Error installing VS Code extension: 1: ENOENT Please restart your IDE and try again.
Resolved 💬 29 comments Opened May 22, 2025 by fcoury Closed Jun 3, 2025
💡 Likely answer: A maintainer (blois, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x] Other: Claude Code
- Claude CLI version: v1.0.1
- Operating System: macOS 15.4
- Terminal: VSCode Terminal
Bug Description
Claude Code Status v1.0.1
Working Directory
L /Users/fcoury/code/paypol
IDE Integration • /config
⚠ Error installing VS Code extension: 1: ENOENT
Please restart your IDE and try again.
Account • /login
L Login Method: Claude Max Account (20x)
L Email: ...
Memory • /memory
L project: CLAUDE.md
Model • /model
LDefault Uses the best available model for Max usage limits (currently
Opus)
Steps to Reproduce
- Open VSCode terminal
- Type claude and enter
- Type /status
Expected Behavior
VSCode Extension is Installed
Actual Behavior
Error installing VS Code extension: 1: ENOENT
Please restart your IDE and try again.
29 Comments
From the same terminal, does
which coderesolve? If not, in VSCode can you try running the commandShell Command: Install 'code' command in PATH?It does:
What does
code --helpreturn - is it actually VSCode or any chance it points to Cursor?Here it goes:
A few more data points:
i am experiencing the same issue, also with v1.02.
Claude CLI version: v1.0.2
Operating System: macOS 15.5 (x86)
Terminal: VSCode Terminal
It works after I manually installed the extension:
Why can't I install claude-code extension in mac os but works perfectly in ubuntu?
I am following their guide by using claude in the integrated terminal for vs-code but it's not working in macos. Claude-code extension not even exists in vs-code extension marketplace at all. But this issue is specific to mac-os (for vs-code, windsurf, and cursor)
Also when using the /config inside claude repl session, macos doesn't show diff auto option at all, while ubuntu does!!
Same issue while using nvm.
Manual installation worked:
code --install-extension ~/.nvm/versions/node/v22.7.0/lib/node_modules/@anthropic-ai/claude-code/vendor/claude-code.vsixInstalling it manually helped! I used this to find the extension:
find ~ -name "*.vsix" 2>/dev/nullI was also able to install manually - thank you @fcoury !
/statusshows:I imagine the cause in my case might be that I have
code-insidersinstalled, andcodeis an alias:Running in Ubuntu in WSL2.
You're welcome! Glad you were able to install it!
This is pure speculation and some analysis of their minimized code, but I think they use the
TERM_PROGRAMenv var to determine it:If yours is also set to
vscodeinside the Insiders (!) terminal, I don't think there should be a problem identifying the environment you're running on. But again, not 100% sure.TERM_PROGRAMis indeed set tovscode- which I think is whyclaudeattempts to install the extension. If I runclaudein a normal WSL terminal outside VSCode,/statusdoes not show theIDE Integration • /configsection.However the
1: ENOENTerror suggests it tried to install something, but failed to find a file or directory...It seems they essentially call
execFile('code',...)- so it fails in my case becausecodeis an alias, not an executable.Ah good catch! I thought it was a symlink and just now realized it's actually an alias 😁
Using a symlink instead of an alias does the trick:
And now if I run
claude /statusinside VSCode terminal I get:So yeah it seems the Claude CLI is not quite smart enough in how it detects and runs the VSCode CLI - although I'm not sure how it could do better
In mine and other mac user's case it weirder:
But we still get the ENOENT error.
Yeah similar setup.
MacOS
fish shell (My suspect)
/Applications/Visual Studio Code.app/Contents/Resources/app/bin/code
(apparently I added this directly to my path? Can't remember doing it).
-rwxr-xr-x 1 blobmueller staff 1160 May 15 07:05 /Applications/Visual Studio Code.app/Contents/Resources/app/bin/code*
but
IDE Integration • /config
✔ Connected to VS Code extension
⚠ Error installing VS Code extension: 1: ENOENT
Please restart your IDE and try again.
Also a few years ago I had code-insiders installed - but now it's uninstalled and I'm running vanilla only.
Okay for me fixed it: my fish.config had a set to add the code binary directly to the PATH - but I also had the symlink present in /usr/local/bin removing /Applications/Visula Studio Code.app/... from PATH fixed it.
Unfortunately not the case for me:
I have the same issue on MacOS. I have node and vscode installed through homebrew (cask). I manually installed the extension and it does show up in the extensions on vscode, but doesn't seem to be installed through claude code /status even though it is connected to the extension.
Claude code doesn't seem to see it.
Code exe is installed in the homebrew /opt/homebrew/bin
The extension bundle is in
/opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/vendorwhere I installed it manually usingcode --install-extensionI encountered the same issue.
I have set the default login shell in VSCode to fish. After changing it to zsh and launching claude, it installed successfully.
```sh
$ code --version
1.100.2
848b80aeb52026648a8ff9f7c45a9b0a80641e2e
arm64
$ claude --version
1.0.5 (Claude Code)
Thanks for your patience folks. We're tracked down the issue (mostly should impact folks using Fish inside VSCode). The fix should be out shortly, will update again once it's out!
This should be fixed in 1.0.10 - please let us know if it works for you!
This worked! thanks
Still experiencing the same issue as today
mikey@Mikeys-MacBook-Pro Web Dev % claude -v
1.0.53 (Claude Code)
Same experiencing the same problem with version 1.0.60
Manual installation does not fix
Same problem here on VSCode Insiders... no problem on VSCode...
echo $TERM_PROGRAMreportsvscodefor both, but VSCode Insiders does not resolvewhich code(onlywhich code-insiders).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.