· Last tested 2026-05-18

Fix Claude Code VS Code Extension Not Working

TL;DR: Verify the CLI is installed and on PATH, check the extension version, restart VS Code, and inspect the output channel for errors.

The Problem

Claude Code is installed but not working in VS Code. Symptoms include:

Why This Happens

The VS Code extension is a thin wrapper around the Claude Code CLI. It fails when:

The Fix

Step 1 — Verify the CLI Is Installed and on PATH

Open VS Code's integrated terminal (Ctrl+`) and run:

which claude
claude --version

If which claude returns nothing, the CLI is not on VS Code's PATH. Fix it:

# Find where claude is installed
npm list -g @anthropic-ai/claude-code

# Common location
ls ~/.npm-global/bin/claude 2>/dev/null || ls /usr/local/bin/claude 2>/dev/null

# Add to VS Code's PATH - edit your shell profile
echo 'export PATH="$HOME/.npm-global/bin:$PATH"' >> ~/.zshrc

Then restart VS Code completely (not just reload window).

Step 2 — Check the Extension Output Channel

  1. Open VS Code Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  2. Type "Output: Focus on Output View"
  3. In the output panel dropdown, select "Claude Code"
  4. Look for error messages

Common errors:

Step 3 — Restart the Extension

  1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  2. Type "Developer: Restart Extension Host"
  3. Wait for extensions to reload

If that does not work, fully quit and reopen VS Code.

Step 4 — Fix Claude Code Terminal Not Responding

If the Claude Code integrated terminal in VS Code is frozen or not responding to input, the underlying CLI process has likely crashed or become disconnected from the extension.

Quick fix: Open VS Code's Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "Terminal: Kill All Terminals". Then open a new terminal with Ctrl+` and test with claude --version. If the version prints, the CLI is fine and the terminal connection was stale.

If the terminal repeatedly freezes after a few commands, your system may be running out of memory. Claude Code sessions can consume significant RAM, especially with large codebases. Check your system memory with Activity Monitor (macOS) or top (Linux). Close other heavy applications or reduce the workspace size by excluding large directories in .vscode/settings.json:

{
  "files.watcherExclude": {
    "**/node_modules/**": true,
    "**/.git/**": true,
    "**/dist/**": true
  }
}

If the terminal still does not respond, try restarting Claude Code completely by running claude --restart in an external terminal (not VS Code's integrated terminal), then reopen VS Code.

Step 5 — WSL-Specific Fix

If you are using VS Code Remote — WSL:

# Inside WSL terminal in VS Code
# Install Claude Code in WSL, not just on Windows
npm install -g @anthropic-ai/claude-code

# Authenticate inside WSL
export ANTHROPIC_API_KEY="sk-ant-api03-your-key-here"
# Or run: claude /login

# Verify
claude --version

The extension in WSL mode uses the WSL environment, not the Windows host.

Step 6 — Verify It Works

After fixes, test in VS Code:

  1. Open the Claude Code panel
  2. Type a simple query: "What is 2+2?"
  3. Verify you get a response

Expected behavior: Claude responds within a few seconds with the answer.

How to Restart Claude Code Extension in VS Code

If Claude Code was working before but stopped responding, a restart often fixes it. There are three levels of restart, from lightest to most thorough:

Level 1 — Restart the Extension Host

  1. Open Command Palette: Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux)
  2. Type Developer: Restart Extension Host
  3. Press Enter

This restarts all extensions without closing VS Code. Takes about 3 seconds. Try this first.

Level 2 — Reload the VS Code Window

  1. Open Command Palette: Cmd+Shift+P / Ctrl+Shift+P
  2. Type Developer: Reload Window
  3. Press Enter

This reloads the entire window, including the terminal and file watchers. More thorough than Level 1 but keeps your open files.

Level 3 — Full Quit and Reopen

# macOS
osascript -e 'quit app "Visual Studio Code"' && sleep 2 && open -a "Visual Studio Code"

# Windows (PowerShell)
Stop-Process -Name code -Force; Start-Sleep 2; code

# Linux
pkill -f code && sleep 2 && code

Use Level 3 when the extension host itself is frozen and the Command Palette is unresponsive. This kills all VS Code processes and starts fresh.

After any restart, test by opening the Claude Code panel and typing a simple query. If it responds, the restart fixed it. If not, the issue is deeper (authentication, PATH, or CLI installation) — follow the full troubleshooting steps above.

Common Variations

Scenario Cause Quick Fix
Terminal not responding / frozen Stale CLI process Kill all terminals, reopen (Step 4)
Works in terminal, not in VS Code Different PATH Add npm bin dir to VS Code terminal profile
Works on first open, fails later Extension crash Restart Extension Host
WSL: extension hangs CLI not installed in WSL Install CLI inside WSL
Input corrupts (Cyrillic chars) Encoding bug (Windows) Update extension, use CLI directly
Panel shows 1M context limit Large project indexing Exclude node_modules from workspace
Cursor IDE: not working Different extension API Claude Code may need Cursor-specific build

Prevention

Written by Michael — solo dev, Da Nang, Vietnam. 50K+ Chrome extension users. $500K+ on Upwork (100% Job Success). Runs 5 Claude Max subs in parallel. Built this site with autonomous agent fleets. See what I'm building

Without a CLAUDE.md — what actually happens:

You type: "Add auth to my Next.js app"

Claude generates: pages/api/auth/[...nextauth].js — wrong directory (you're on App Router), wrong file extension (you use TypeScript), wrong NextAuth version (v4 patterns, you need v5), session handling that doesn't match your middleware setup.

You spend 40 minutes reverting and rewriting. Claude was "helpful."

With the Zovo Lifetime CLAUDE.md:

Same prompt. Claude reads 300 lines of context about YOUR project. Generates: app/api/auth/[...nextauth]/route.ts with v5 patterns, your session types, your middleware config, your test patterns.

Works on first run. You commit and move on.

That's the difference a $99 file makes.

Get the CLAUDE.md for your stack

Related Guides

I hit this exact error six months ago. Then I wrote a CLAUDE.md that tells Claude my stack, my conventions, and my error handling patterns. Haven't seen it since.

I run 5 Claude Max subs, 16 Chrome extensions serving 50K users, and bill $500K+ on Upwork. These CLAUDE.md templates are what I actually use. Not theory — production configs.

Grab the templates — $99 once, free forever

47/500 founding spots. Price goes up when they're gone.

Related Issues

If you debug browser extensions alongside VS Code work, Zovo's developer tools streamline the inspect-reload-test cycle for Chrome extensions.

Try it: Paste your error into our Error Diagnostic for an instant fix.

Last verified: 2026-04-14. Found an issue? Open a GitHub issue.

Related Articles

→ Try the Error Diagnostic Tool — paste your error message, get the fix instantly