What is the exact message?
The Claude Code program for this computer, the Linux (linux-x64) build, could not be found.The build in the middle changes with the machine: linux-x64 here, and on a Windows machine the same line names the win32-x64 build. The message is printed by the extension rather than by Claude Code itself.
What does it mean?
The extension ships its own copy of Claude Code so the panel works without a separate install. On startup it looks for the copy built for your platform and architecture, and this message means there is none in the package it loaded.
Anthropic's own description is exactly that: the extension looked for the copy of Claude Code bundled inside it and found none built for your computer, so the message names the build your computer needs.
What causes it
- The extension package is for another platform. Anthropic's own first route says it plainly: when the message names a build, you have the extension package for another platform.
- The package holds no build for your computer at all. Anthropic's second route covers a package that does not say which build it holds, which is why a reinstall is the step for that case.
- The extension cannot use the copy it has. Whatever the reason, its own answer is the same three routes, and a wrapped
claudesidesteps the bundled copy entirely.
This is the extension's own message, so having claude on your PATH does not prevent it. A different message, Could not locate the Claude CLI on PATH, is the extension saying it never found the CLI at all.
How do I fix it?
- Read the build in the message. It is the identifier after the platform name, such as
linux-x64orwin32-x64, and it names what your computer needs. - Install the extension package made for that build. If the message tells you which build is involved, you have a package for another platform, so install the one built for the platform named. The VS Code extension guide has the Extensions-view install steps, including the direct install links.
- If no build is named, reinstall the extension from your editor's Extensions view. That is Anthropic's route for a package that does not say which build it holds.
- Or point the extension at your own Claude Code. Set
claudeCode.claudeProcessWrapperto a separately installedclaudebinary. Anthropic gives this as a route in either case, and it also sidesteps the bundled copy entirely.
On a build before v2.1.290 the same failure read Unsupported platform: <platform>-<arch>. No compatible Claude Code binary found. If you see that text instead, you are on an older build and the same three routes apply.
How do I know it is fixed?
- The message is gone and the Claude Code panel opens a session instead.
- With
claudeProcessWrapperset, the panel starts the binary you named, andclaude --versionin a terminal reports the same version. - Reloading the editor window does not bring the message back.
Where these answers come from
- The message, what the extension looked for, the three routes and the pre-v2.1.290 wording: Anthropic's error reference, read November 18, 2026.
- The setting name and what a process wrapper does: Anthropic's VS Code extension settings, read November 18, 2026.
Common questions
What is the extension looking for?
The copy of Claude Code bundled inside the extension, built for your computer. Anthropic's wording is that the extension looked for that copy and found none built for your computer, and the message names the build your computer needs.
How do I know which package to install?
Read the build in the message, such as linux-x64 or win32-x64, and install the extension package made for that build. That is Anthropic's first route when the message names a build.
What if the message names no build at all?
Reinstall the Claude Code extension from your editor's Extensions view, which is the route Anthropic gives for that case.
Can I avoid the bundled copy entirely?
Yes. Set claudeCode.claudeProcessWrapper to a separately installed claude binary, which Anthropic lists as a route in either case.