When Claude Code does not work in VS Code, check four things in order: the extension is installed and the window reloaded, VS Code is 1.94.0 or later, the workspace is trusted, and the standalone claude command is on PATH. The extension bundles its own CLI for the chat panel, but terminal use needs a separate install.
When Claude Code does not work in VS Code, check four things in order: the extension is not installed or loaded, VS Code is older than 1.94.0, the workspace is in Restricted Mode, or the standalone claude command is missing from PATH. The extension bundles its own copy of the CLI for the chat panel, but typing claude in a terminal needs a separate standalone install.
Compared with the VS Code page, the error reference and the install troubleshooting page as read in November 2026. Every step here is taken from those pages, not run in the extension. If the panel loads but replies never arrive, check the Claude Code status hub first.
Which symptom do you have?
| Symptom | Likely cause | What to do |
|---|---|---|
| No Spark icon in the editor toolbar | No file open, old VS Code or Restricted Mode | Open a file, check Help > About for 1.94.0+, trust the workspace |
| Extension will not install | VS Code older than 1.94.0, or no permission to install extensions | Check the version, check permissions, or install from the Visual Studio Marketplace |
No available IDEs detected from /ide | Extension not installed (from CLI 2.1.318, the integrated terminal does not install it for you) | Install the extension, then restart claude |
claude not found in the integrated terminal | Standalone CLI not installed or not on PATH | Install the CLI, then run claude --version |
Claude Code did not finish starting | Startup exceeded 60000ms; the docs name slow plugins, MCP servers, hooks, disks or network | Open the output logs, then follow the error reference entry |
Panel blank or Claude Code couldn't load | Old extension build | Update to 2.1.309+, reload, then open the logs |
| Ctrl+J adds a newline in the prompt box | Default keybinding | Unbind it in keybindings.json (extension 2.1.309+) |
Why can't I see the Spark icon?
The docs list five checks. Open a file, because a folder alone is not enough. Confirm VS Code is 1.94.0 or later under Help > About. Run Developer: Reload Window from the Command Palette. Temporarily disable other AI extensions such as Cline or Continue. Check workspace trust, since the extension does not work in Restricted Mode. As a workaround, click the Claude Code item in the status bar, which works with no file open, or use the Command Palette (Ctrl+Shift+P) and type "Claude Code".
How do I connect the terminal to VS Code?
There are two paths, both from the docs. In VS Code's integrated terminal (Ctrl+` on Windows), install the extension, then run claude; it connects automatically. On Claude Code 2.1.318 or later the CLI no longer installs the extension for you, so until you do, /ide reports No available IDEs detected and /status shows the IDE as not connected. From an external terminal, run /ide inside Claude Code to connect to a running VS Code window. If VS Code is running without the extension, the docs say /ide installs it, unless autoInstallIdeExtension is turned off.
The extension and CLI share conversation history, so claude --resume in a terminal picks up an extension conversation. If you only installed the extension, claude will not exist on PATH. Run the standalone install, then check it:
claude --version
On Windows the installer puts claude.exe in %USERPROFILE%\.local\bin. A terminal inside an editor takes its PATH from the editor, so quit and reopen VS Code after fixing PATH. The steps are in the Windows and WSL install guide.
What do the startup errors mean?
The VS Code page maps these messages to entries in the error reference: Claude Code process exited with code 1, Claude Code did not finish starting or Subprocess initialization did not complete within 60000ms, Could not locate the Claude CLI on PATH, and The connection to Claude Code ended before this message completed. Match your exact text there rather than guessing. The Claude Code process exited with code N entry says the real error is in the process output, which you reach from the View output logs link. For the 60000ms error, the docs say that in VS Code the first 10 minutes of reported SessionStart or Setup hook time do not count toward the limit, and that before extension v2.1.304 all hook time counted, so update the extension first. Two GitHub issues are still open: issue 50559 collects Windows and macOS reports of the 60000ms error, with conflicting versions and causes that include invalid settings entries and slow plugins, and issue 93795 was filed on extension 2.1.269, before that change. Both are user reports, not confirmed by Anthropic.
What if sign-in or the network is the problem?
Not logged in · Please run /login: the extension reopens the sign-in screen. If it does not, run Developer: Reload Window.ANTHROPIC_API_KEYis set but you still get the prompt: VS Code may not have inherited your shell environment. Launch it withcode .from a terminal, or sign in with your Claude account.- Behind a corporate proxy that inspects encrypted traffic, dictation and the Web tab can fail with
unable to get local issuer certificate. The docs say to setNODE_EXTRA_CA_CERTSin theenvblock of~/.claude/settings.jsonto your proxy's root CA file, written without~, and with each backslash doubled on a Windows path. This needs extension 2.1.307 or later. - In a WSL, SSH or dev container window, edit
settings.jsonand save certificate files on that remote system, not your local machine.
If sign-in errors persist, see what "Authentication service was unavailable" means to rule out a provider-side problem.
What if the panel never responds?
The VS Code page's checklist for a panel that never responds is short: check your internet connection, start a new conversation, and run claude in a terminal to see more detailed error messages. If the problem persists, it points to filing an issue on GitHub with details of the error. Garbled glyphs in the integrated terminal are a separate problem; the troubleshooting page says /terminal-setup sets the terminal's GPU acceleration to off. For a health check outside the editor, claude doctor prints installation and settings diagnostics from your shell. Claude Code: Show Logs opens the extension's log.
More practical writing for people building with AI tools is on the Lead Source blog.
Fixed? Two optional things
Check Anthropic’s status and get an alert when an incident is resolved: Claude Code status and alerts, an independent resource by Lead Source.
Official source: status.claude.com.
Written by the team at Lead Source, where the day job is lead source tracking: working out which marketing actually brings customers.