← All guides

TroubleshootingSetup

Claude Code Not Working in VS Code: Missing Icon, Blank Panel, PATH and Exit Code Errors

By Neo Zino - builder of ClockedCode·Updated October 23, 2026·11 min read

Claude Code broken in VS Code? Find your symptom: no Spark icon, a blank panel, a PATH error or exit code 1. Each has a one-step fix. Tested on 2.1.309.

Made with DispatchSEO

Open a file, then run Developer: Reload Window from the Command Palette. If Claude Code still does nothing in VS Code, the cause is almost always one of five things: no file open, a stale extension, a Windows PATH problem, an untrusted workspace, or a crash you can read in the log. The table below matches each symptom to its first move.

TL;DR: Open a file, check VS Code is 1.94.0 or later, update the extension to the latest version, and reload the window. Trust the workspace. On Windows, a "Could not locate the Claude CLI on PATH" error means the system PATH, not your PowerShell profile, is missing the install folder, and VS Code has to be restarted after you fix it.

What does a broken Claude Code extension actually look like?

There is no single "not working". The extension fails in six distinct ways, and each one has a different first move. Match yours before touching anything, because the fix for a missing icon does nothing for an exit code.

Everything in that grid comes from the VS Code page of the official docs and the Claude Code error reference. If your problem is more general than the editor, such as login loops or a dead claude command everywhere, the broader Claude Code not working checklist is the better start.

Why is the Spark icon missing when the extension is installed?

Because the icon is not always drawn. It sits in the editor toolbar at the top right and only appears while a file is open. A folder with no file selected hides it. It looks exactly like an extension that failed to install.

Work through these in order:

1. Open any file.
2. Check Help > About. The docs list VS Code 1.94.0 or later as the requirement. (My own VS Code setup guide still says 1.98.0 in one place; go by the docs number.)
3. Run Developer: Reload Window.
4. Temporarily disable other AI extensions such as Cline or Continue.
5. Trust the workspace. The extension does not run in Restricted Mode, and the shield icon in the status bar is where you grant trust.

You can skip all of it for the moment by clicking the Claude Code item in the status bar at the bottom right, or by typing "Claude Code" in the Command Palette. Both work with no file open. If the extension is not in the Extensions view at all, install it from the Marketplace listing directly.

What if the panel opens but it is blank or "couldn't load"?

A panel that shows nothing, not even the prompt box, is fixed by extension v2.1.309 or later, per the docs. Update the extension in the Extensions view, then run Developer: Reload Window.

If a Claude Code couldn't load notice appears after that, it lists steps. Work through them in order. If the panel is still empty, run Claude Code: Show Logs and send that log with a bug report. The log lands in an output channel named Claude VSCode, which is also where you look for anything else in this post.

Two related cases have their own fix. A panel that crashes or shows only Something went wrong every time a reload brings your conversation back needs extension v2.1.301 or later. After two failed reopenings in a row you get a fresh chat and a notice that the old one was not reopened. And a resumed conversation that sits blank for a second is normal: it is waiting for the process to start, and Waiting for your plugins… shows after about a second. The messages appear on their own, or after 20 seconds at most.

Why does the panel work but claude fail in the terminal?

Because they are two separate copies of Claude Code. The extension carries a private binary for its chat panel. Typing claude in a terminal runs the standalone CLI, which the extension does not install and does not put on your PATH.

So "Claude works in the panel but claude: command not found in the terminal" is not a contradiction. It is the documented behavior. Install the standalone CLI once, make sure its folder is on your PATH, and the commands on the VS Code page, such as claude mcp add and claude --resume, work in any terminal. The fix for the PATH half is its own guide: claude: command not found.

To confirm the standalone install is healthy, run this in the integrated terminal:

claude doctor

On a clean native install of 2.1.309 it opens with these lines (I ran it on Linux while writing this; your path will differ):

Claude Code doctor

Running: native (2.1.309)
Platform: linux-x64
Path: /home/runner/.local/share/claude/versions/2.1.309
Config install method: native
Auto-updates: enabled

If Running shows a version much older than the extension, or Path points somewhere you did not expect, you have two installs fighting. That is worth knowing before you blame VS Code.

Why does Windows say it "could not locate the Claude CLI on PATH"?

This one is Windows-only, and the full message is long, but the cause is short. When you open Claude Code in the integrated terminal and its shell is PowerShell, the extension refuses to launch by name. A bare claude in PowerShell could run a claude file sitting in the open folder instead of the installed CLI, so the extension blocks the launch until it can find the real one on PATH.

The docs give three steps:

1. Open a new PowerShell window outside VS Code and run where.exe claude. If it prints nothing, the CLI is not on your PATH, and you add its install folder under Verify your PATH.
2. Set the entry as a user or system environment variable. A PATH edit that lives only in your PowerShell profile never reaches the extension, because the extension does not run your profile.
3. Restart VS Code. It captures PATH when it starts, so a change only takes effect after a restart. A reload of the window is not enough.

The third step is the one people miss. You fix the PATH, reload, and the same error comes back. Close VS Code fully.

What do "exited with code 1" and "connection ended" actually mean?

Both are the extension reporting that the claude process behind the panel stopped, not a diagnosis. The exit code alone does not say what failed.

Claude Code process exited with code 1: click the View output logs link shown with the error. Then run claude in a terminal in the same folder. The failure usually reproduces there with its real error message, which you can look up in the error reference.

The connection to Claude Code ended before this message completed: the extension sent your message and the connection closed before it was acknowledged, so it cannot tell whether the message was processed. Send it again. The next message starts a fresh process that resumes the conversation. If it repeats, use the same terminal test.

A Windows detail worth knowing: the native build can exit with code 4294967295 right after a turn finishes. Since v2.1.273 the extension closes the session quietly in that case and your next message resumes the conversation. Before that version it showed the error even though nothing was lost, so on an old extension that scary code can be harmless.

If prompts simply get no reply and there is no error, the docs' three checks are the right ones: confirm your connection, start a new conversation, and run claude in a terminal for a clearer message. A dropped login shows up the same way, and signing in again is covered in Claude Code not working. If you suspect the service rather than your machine, check whether Claude Code is down first.

Does it behave differently over WSL, SSH or code-server?

It can, because the extension runs where VS Code's remote window runs. I will keep this section short, because I could only verify part of it.

What I can source: the official VS Code page documents claudeCode.claudeProcessWrapper, an executable the extension uses to launch the Claude process. It exists for the case where the extension build does not include a binary for your platform, and you point it at a separately installed claude. For WSL specifically, install the CLI inside WSL and install the extension into the WSL window, as laid out in the Claude Code on WSL guide.

What I could not verify: the hang at "API Request" on Code-Server. The page that ranks for it is a bug report against a different extension (Roo Code), not Claude Code's own extension, and the official docs do not describe a code-server fix. If you hit it, run the terminal test from the last section: if claude works there, the problem is in how the extension reaches it, and if it fails there too, you are looking at a network or login problem rather than VS Code.

Behind a TLS-inspecting corporate proxy, dictation and the Web tab fail with unable to get local issuer certificate. The fix is NODE_EXTRA_CA_CERTS in the env block of ~/.claude/settings.json, on extension v2.1.307 or later, and the docs warn that the VS Code setting claudeCode.environmentVariables does not apply to those two features.

How do you wipe the extension and start clean?

Go up the ladder and stop at the first rung that works. Each rung costs more than the one before it.

The last rung is the documented full reset. Uninstall from the Extensions view (Ctrl+Shift+X, search "Claude Code", Uninstall), then delete the extension's storage folder:

# macOS
rm -rf ~/Library/"Application Support"/Code/User/globalStorage/anthropic.claude-code

# Linux
rm -rf ~/.config/Code/User/globalStorage/anthropic.claude-code

# Windows, PowerShell
Remove-Item -Recurse -Force "$env:APPDATA\Code\User\globalStorage\anthropic.claude-code"

That deletes the extension's data and settings, so do it last. Do not expect it to stay uninstalled if you use the terminal: running claude in a VS Code integrated terminal reinstalls the extension automatically. To stop that, turn off Auto-install IDE extension in /config, set autoInstallIdeExtension to false, or set the CLAUDE_CODE_IDE_SKIP_AUTO_INSTALL environment variable to 1.

When this checklist is the wrong tool

Skip it if the problem is not the editor. Login loops, billing errors and rate limits behave the same in a plain terminal, so the general troubleshooting checklist is faster. Skip it too if claude works in the panel and you only wanted it in the terminal; that is a PATH issue, not a broken extension.

What I did not test: the Windows-only errors, because I build on Linux, and the remote cases. Those come from the current docs, quoted as written, not from a run of my own. Versions move quickly, so if your extension is far from 2.1.309, update it before trusting any step above. If you want a setup where a fresh install just works, that is what the ClockedCode dashboard is for.

FAQ

Why can't I see the Claude Code icon in VS Code?

The Spark icon only shows in the editor toolbar when a file is open, so a folder with no open file hides it. Open a file, check VS Code is 1.94.0 or later under Help > About, run Developer: Reload Window, and make sure the workspace is trusted. The Claude Code item in the status bar works even with no file open.

Why does the Claude Code panel open blank?

A panel that shows nothing at all, not even the prompt box, is fixed by updating the extension to v2.1.309 or later and running Developer: Reload Window. If a Claude Code couldn't load notice appears afterwards, work through the steps it lists in order. If the panel is still blank, Claude Code: Show Logs opens the log to attach to a bug report.

Does installing the extension put claude on my PATH?

No. The extension bundles a private copy of the CLI for its chat panel, so the panel can work while typing claude in a terminal says command not found. To run claude in a terminal you need the standalone CLI install, and then a PATH that includes its folder.

What does "Claude Code process exited with code 1" mean?

The claude process behind the panel stopped with an error, and the exit code alone does not say why. Click the View output logs link shown with the error, then run claude in a terminal in the same folder, where the real error message usually reproduces.

How do I fully reset the Claude Code extension in VS Code?

Uninstall it from the Extensions view, then delete the anthropic.claude-code folder under VS Code's globalStorage directory for your platform to remove its data and settings. If you run claude in a VS Code terminal, it reinstalls the extension on its own unless you turn off Auto-install IDE extension in /config.