Using Claude Code in VS Code: Setup, Shortcuts & Tips (2026)

re-verified against the official docs at code.claude.com/docs/en/vs-code (accessed 08/10/2026).

Quick clarification: what does "claude code vs code" mean?

If you typed "claude code vs code" expecting a head-to-head comparison against some other tool, you are on the wrong page. Here "vs code" = Visual Studio Code, so the real question is how to use Claude Code integrated inside VS Code - not a showdown. (Actually looking for a real comparison? Start with what Claude Code is to get the basics down first.)

One more common mix-up: this article is about the official "Claude Code" extension (publisher anthropic.claude-code, Spark icon ✱, with diff/plan/checkpoint), not the older "Claude AI" chat-sidebar extension that a lot of guides walk you through. They are completely different products. The official extension understands your whole workspace, edits multiple files in one pass, and returns a diff for you to review; the older chat extensions are mostly a question-and-answer box next to your code. If a guide never mentions the Spark icon, diff review, or plan mode, it is almost certainly talking about a different product.

What you need first (requirements)

Before installing, check three things so you don't waste time:

• A recent VS Code build - the official docs list version >= 1.94.0. Check under Help -> About, and update first if yours is too old.
• A paid Claude plan: Pro, Max, Team, or Enterprise (or access through the Claude Console). This is a hard requirement.
• No API key, no free tier. The extension signs in with your Claude account rather than a pasted key like some other tools. If you don't have a plan yet, you won't be able to use it - that is a real difference from some third-party AI extensions that let you plug in your own API key.

Let's be honest about the limitation: because it depends on a paid plan, this isn't the option for anyone hoping to use it for free. The upside is that you never manage API quotas or get surprised by a token bill - usage stays inside your subscription. If you're torn between plans, pick by how often you'll use it: Pro is plenty for trying things out or learning, while Max earns its price if you're in the tool all day.

Not sure yet what Claude Code is or how far it goes? Read the Claude Code intro, then come back here to install the extension.

How to install the Claude Code extension for VS Code (step by step)

The whole thing takes about two minutes. Four steps:

1. Open the Extensions tab with Ctrl+Shift+X (Windows/Linux) or Cmd+Shift+X (macOS). Type "Claude Code" in the search box, pick the extension from publisher Anthropic (don't confuse it with the other "Claude AI" extensions), and click Install.
2. Open the Claude Code panel by clicking the Spark icon ✱. It shows up in the Editor Toolbar (top-right when a file is open), the Activity Bar on the left, or the Status Bar at the bottom. Tip: you need at least one file open for the icon to appear clearly.
3. Sign in: click Sign in and VS Code opens your browser to authenticate with your Claude account. Come back to VS Code and the panel is ready.
4. Send a test prompt: try something simple like "explain what this file does" to confirm everything works. If Claude answers and picks up the file you have open, the install is good.

One habit worth starting with: after installing, open the actual project folder (not a single loose file) so Claude sees the full workspace context. On Windows, if you work in WSL, open the project in VS Code's WSL mode as usual and then bring up the panel - the extension runs fine in that environment.

This extension isn't limited to stock VS Code - it also installs on Cursor, Kiro, and Open VSX-based builds, with the same steps. If you also want the claude command in your terminal, see the full Claude Code CLI install guide (the extension and CLI complement each other, more on that below).

The interface and core features inside VS Code

Compared to typing commands in the terminal, the extension gives you a much more visual interface. Here are the features worth using:

• Side-by-side diff review: whenever Claude edits a file, the change shows up as a side-by-side diff, clearly green and red. You review it one change at a time, accept or reject each one individually, and can even edit directly in the diff before accepting. It's a world away from pasting code out of a chat and merging by hand - you always see exactly what's about to change and can block it line by line. This is the single strongest reason to work in VS Code.
• Plan mode: in Plan mode, Claude opens a plan as Markdown so you can read it and comment inline before it touches any code. It's a great fit for big tasks: you review the direction, tweak a few spots in the plan, and only then let it run - no more watching the AI charge into a dozen files at once. To go deeper on the planning workflow, see the 10 first steps for beginners.
• @-mention to add context to a prompt: @file#5-10 (just lines 5-10), @folder/ (a whole folder), @terminal:name (pull in terminal output), and @browser (control Chrome). Instead of copy-pasting, you point Claude straight at what it needs to see. When debugging, for example, @file#40-72 keeps Claude on the exact broken function instead of reading a thousand-line file - more accurate and cheaper on tokens.
• Checkpoint / Rewind: roll file changes back to an earlier state if Claude heads the wrong way - a safety net, so you don't lean entirely on git stash or step-by-step Ctrl+Z.
• Session history + multiple tabs: run several sessions in parallel and revisit past conversations, handy when you're juggling threads - one tab mid-refactor, another for a quick API question.
• Permission mode: right in the prompt box, choose Manual (approve each action by hand), Plan (planning only), or Edit automatically. Keep it cautious in an unfamiliar repo and loosen up once you trust it. You can set a default up front via initialPermissionMode in settings.

Claude Code keyboard shortcuts in VS Code

Here is the full shortcut table (from the official docs) that most guides leave out:

Forget one? Open the Command Palette (Ctrl/Cmd+Shift+P) and type "Claude Code" to see every command. For a printable roundup of everything, see the Claude Code cheat sheet.

Tips to get the most out of Claude Code in VS Code

Anyone can install it, but running it smoothly takes a few tricks. These are the ones I use daily:

• Move the panel to the secondary sidebar: so Claude sits next to your code instead of covering the editor. Just drag the Spark icon to the right edge - seeing the diff and the code at once is much easier.
• Write a CLAUDE.md as your "project memory": this is the single biggest quality boost. Put conventions, stack, and test commands in this file so Claude doesn't have to guess. See how to write a solid CLAUDE.md.
• Use @terminal instead of copy-pasting errors: run the failing command in the integrated terminal, then @terminal drops the whole output into your prompt - faster and with more context than pasting by hand.
• Toggle useTerminal: if you prefer a CLI feel, turn this on in settings; if you want a pure GUI, turn it off.
• Consider autosave and respectGitIgnore: to keep diffs clean and stop Claude from reading junk or sensitive files by accident.
• Track your cost: type /usage to check consumption, and /compact to compress context when a chat gets full - it keeps Claude focused and saves tokens.
• Keep a tidy statusline: customize it to see your current model and cost at a glance - see the statusline customization guide.

One habit worth building: before you hand off a big task, spend 30 seconds spelling out the goal and constraints in the prompt (or keep them in CLAUDE.md), then flip on Plan mode to review the direction before letting it edit. It costs one extra beat but sharply cuts how often Claude drifts off target, saving you rewinds. In a large repo, pair it with @folder/ for the module you're working on instead of dropping the whole project on it - Claude stays focused, output is cleaner, and it costs fewer tokens.

Extension vs CLI - which should you use?

A common question: once you have the extension, do you still need the CLI? Quick comparison:

Important note: the extension does not add the claude command to your PATH, so to type claude in the integrated terminal you have to install the standalone CLI separately. Practical advice: use both - the GUI to review diffs and plans, the CLI for quick actions - and they share the same history, so you can claude --resume to pick a session back up. Full CLI install details are in the complete Claude Code install guide.

Common problems and how to fix them

A few frequent issues and quick fixes:

• Cmd+Esc not working on macOS Tahoe: that shortcut is often grabbed by the Game Overlay. Go to System Settings -> Keyboard -> Keyboard Shortcuts -> Game Controllers and uncheck the item claiming it, or rebind Claude Code: Focus input to another combination in VS Code's Keyboard Shortcuts.
• No Spark icon ✱: check in order - do you have at least one file open? Is VS Code >= 1.94.0? Try Reload Window (Command Palette), temporarily disable other conflicting AI extensions, and enable workspace trust for the project folder.
• "Please run /login": try Reload Window, or close VS Code and reopen the project with code . from the terminal so it picks up the right signed-in session.
• Claude isn't responding: check your network, open a new session, or try the CLI to narrow down whether the problem is the extension or your account. If the chat has gotten very long, type /compact to compress context and try again.
• Diffs don't appear or apply to the wrong place: make sure the file is saved and isn't being overwritten by another extension (a formatter running on save). Use controlled autosave and temporarily disable format-on-save while reviewing a large diff.

Run into something not on this list? See the roundup of common Claude Code errors and how to fix them.

Level up with prebuilt skills and subagents

The extension gets a lot stronger when your Claude Code already has a set of skills, subagents, and workflows instead of you building them from scratch. If you want to move fast, one option is the AgentKit kit for Claude Code - a packaged set of skills and agents for dev and marketing work; you can give AgentKit a try (20% off via link) to see whether it fits your workflow. It's not required: the stock extension is plenty on its own, and a kit is just an optional way to go faster.

Frequently asked questions (FAQ)

Is Claude Code in VS Code free?

No. The extension installs for free, but to use it you need a paid Claude plan (Pro, Max, Team, or Enterprise) or access through the Claude Console. There is no free tier and you can't use it with an API key.

Do I need a Pro plan?

You need at least one paid plan; Pro is the lowest tier that works for an individual. Max suits heavy use, while Team and Enterprise are for groups.

How is it different from the "Claude AI" extension, Cline, or Continue?

The "Claude Code" extension is the official Anthropic build (publisher anthropic.claude-code), with diff review, plan mode, checkpoints, and @-mention tied to your Claude account. Extensions like the older "Claude AI" chat, Cline, and Continue are different products that work and feel differently.

Can I use it in Cursor?

Yes. The Claude Code extension installs on Cursor, Kiro, and Open VSX-based editors, with the same steps as on VS Code.

Do I need to install the CLI separately?

Not necessarily. The extension already bundles a CLI for the panel. You only need the standalone CLI if you want to type the claude command in the integrated terminal, since the extension doesn't add claude to your PATH.

Does it work on Windows/WSL?

Yes. The extension runs on Windows, macOS, and Linux; for WSL, open the project in VS Code's WSL mode as usual and then use the Claude Code panel.

Conclusion and next steps

That's Claude Code running right inside VS Code: install the official extension, sign in with a paid plan, then lean on diff/plan/checkpoint, @-mention, and the shortcuts to code faster. Next step: if you're just starting, read the 10 first steps for beginners; if you also want the command line, see the complete Claude Code CLI install guide. Happy coding.