Claude Code VSCode: The Official Extension Guide (2026)

Claude Code VSCode integration comes through one official extension: "Claude Code for VS Code" by Anthropic, which puts the full Claude Code agent in a native sidebar panel with inline diff review, plan mode, and checkpoints. As of July 2026 the extension sits at version 2.1.201 on the VS Code Marketplace with over 19.6 million installs, and it requires VS Code 1.98.0 or newer plus a Claude Pro, Max, Team, Enterprise, or Console account. This guide covers installation, every major feature, how the extension compares to the terminal CLI, settings, and the fixes for the most common problems.

What the Claude Code VS Code Extension Is

The Claude Code VS Code extension is Anthropic's official graphical interface for Claude Code, published under the extension ID anthropic.claude-code. Instead of driving the agent from a terminal, you get a chat panel docked in the sidebar (or as an editor tab) that can read your open files, see your text selection, pull language-server diagnostics from the Problems panel, and apply multi-file edits that you review as native VS Code diffs.

Under the hood it is the same engine as the terminal tool, so your CLAUDE.md memory files, settings.json permissions, and session history carry over between the two. If you are brand new to the tool itself, start with our complete Claude Code guide and the installation walkthrough, then come back here for the IDE layer. The official reference lives at code.claude.com/docs/en/vs-code.

How to Install Claude Code in VS Code

Installing Claude Code in VS Code takes under a minute through the Extensions view: press Cmd+Shift+X (Mac) or Ctrl+Shift+X (Windows/Linux), search for "Claude Code", and click Install on the listing published by Anthropic. You need VS Code 1.98.0 or newer.

Three details trip people up:

• The extension bundles its own CLI copy for the chat panel, so the panel works immediately after install. But typing claude in the integrated terminal still requires the standalone CLI install, because the extension does not add claude to your shell PATH.
• Auto-install works in reverse too: if you already have the CLI and run claude inside VS Code's integrated terminal, it can install the extension for you.
• Authentication happens through a browser OAuth flow with your Claude account (Pro, Max, Team, or Enterprise) or Console credentials for API billing. No API key is pasted anywhere for subscription users.

The same extension installs in VS Code forks: Cursor (via the cursor:extension/anthropic.claude-code URI), Windsurf, VSCodium (through the Open VSX registry), and others that support VSIX. JetBrains IDEs like IntelliJ, PyCharm, and WebStorm use a separate JetBrains plugin that does not bundle the CLI at all.

Features: Panel, Diffs, Plan Mode, Checkpoints

The extension's core value is that Claude Code's actions become visible IDE objects instead of terminal text. As of July 2026 the documented feature set includes:

• Sidebar panel or editor tabs. Run Claude docked in the sidebar, as a full editor tab, or in multiple tabs and windows at once for parallel sessions.
• Inline diff review. Proposed changes open as side-by-side diffs in VS Code's native viewer before you accept them, which is far easier to scan than terminal diffs.
• Plan mode. Claude writes its plan as a full markdown document you can comment on inline before any file is touched. Our plan mode guide covers when to use it.
• @-mentions. Reference files with @filename or line ranges with @filename#start-end, with fuzzy matching. Selecting text in the editor automatically adds it to context.
• Checkpoints and rewind. Hover over any message to fork the conversation, rewind the code, or both, so a bad edit run is reversible.
• Diagnostics sharing. The built-in IDE MCP server exposes Problems-panel errors to Claude through the mcp__ide__getDiagnostics tool, so it sees type errors without you pasting them.
• MCP management in chat. Type /mcp to view and authenticate MCP servers without leaving VS Code; adding new servers is easiest via the CLI, as covered in our Claude Code MCP guide.
• Session history and remote sessions. Search and resume past conversations, including cloud sessions started on claude.ai, from the Session History and Remote tabs.
• Permission modes. Switch between Manual, Plan, Edit Automatically, and Bypass at the bottom of the prompt box.

Keyboard Shortcuts

Five shortcuts cover most of the extension workflow, documented in the official VS Code docs:

Extension vs Terminal CLI: Which Should You Use?

The VS Code extension and the terminal CLI share the same engine, memory files, and session history, so this is a question of interface, not capability tiers. The extension wins on reviewability; the CLI wins on completeness and scriptability.

A practical split that holds up: use the extension for interactive feature work where you want to read every diff, and drop to the CLI for scripted runs, CI usage, hook-heavy setups, and MCP administration. Both respect the same CLAUDE.md memory hierarchy, which we cover in depth in our Claude Code memory guide.

Settings and Configuration

Extension settings live in VS Code's own settings UI (search "Claude Code" under Extensions), while agent behavior stays in the shared ~/.claude/settings.json and project-level .claude/settings.json files. The most useful extension-specific options as of July 2026:

• initialPermissionMode: start sessions in default (manual approval), plan, acceptEdits, or bypassPermissions.
• preferredLocation: sidebar or panel for where conversations open.
• useTerminal: launch the terminal interface instead of the graphical panel.
• autosave: auto-save files before Claude reads or writes them (on by default).
• respectGitIgnore: keep ignored files out of context (on by default).
• allowDangerouslySkipPermissions: adds the Bypass option to the mode selector; leave this off unless you understand the risk.

Project instructions, coding conventions, and persistent context belong in CLAUDE.md, not in settings. Our Claude Code best practices post covers how to structure both.

Troubleshooting the Claude Code VS Code Extension

Most Claude Code VS Code problems come down to version requirements, PATH issues, or a stale window. The documented fixes:

• Extension will not install or the spark icon is missing: confirm VS Code is 1.98.0 or newer, open a file, then run "Developer: Reload Window". Conflicting extensions can also hide the icon.
• claude not found in the integrated terminal: the extension does not install the shell command. Install the standalone CLI and launch VS Code with code . from a terminal so it inherits your PATH.
• Cmd+Esc does nothing on macOS: on macOS Tahoe and later, the system Game Overlay shortcut intercepts it. Disable it under System Settings, Keyboard, Game Controllers, or rebind the key in VS Code.
• Login loops or auth errors: unset any old ANTHROPIC_API_KEY environment variable, and on SSH or WSL2 paste the login code manually instead of waiting for the localhost callback. More fixes in our Claude Code login fix guide.
• Claude stops responding: start a new conversation, or run the same prompt in the CLI to see detailed errors, then run /doctor for diagnostics.

Limitations and Tradeoffs

The extension is not a full replacement for the terminal: hooks, the ! bash shortcut, tab completion, and parts of MCP configuration remain CLI territory, and the panel exposes only a subset of slash commands. Teams that lean on scripted or headless Claude Code runs will still live in the terminal most of the day.

Cost is the other honest caveat. There is no free tier for Claude Code in any interface; you need at least Claude Pro at $20 per month or Console pay-as-you-go billing, and heavy agentic sessions consume plan usage quickly. If you are comparing the extension against agent-native editors before committing, our Claude Code vs Cursor comparison is the place to start.

Related Guides

• How to Install Claude Code on Mac, Windows, and Linux
• Claude Code Commands: The Complete Cheat Sheet
• Claude Code Memory: CLAUDE.md and the Memory System
• Claude Code Changelog: What's New, Version by Version