How to Set Up Claude Code in VS Code (2026 Guide)

A practical, no-fluff walkthrough for getting Claude Code running inside VS Code — from install to your first real coding task.

If you’ve been coding with AI in 2026, you’ve probably heard of Claude Code. It’s Anthropic’s agentic coding tool — instead of copy-pasting snippets into a chat window, you give it a task and it reads your codebase, edits files, runs commands, and iterates until the job is done.

How to Set Up Claude Code in VS Code (2026 Guide)

It started as a terminal tool, but the VS Code integration is where it really shines for day-to-day work: you get inline diffs, file context, and the agent working right next to your editor.

This guide covers everything: installation, authentication, the VS Code extension, and the workflow tips that actually matter.

What You Need Before Starting

• VS Code — a recent version (update it if you haven’t in a while)
• Node.js 18 or newer — only needed if you install via npm; check with node -v
• A way to pay for Claude — either a Claude Pro/Max subscription or an Anthropic Console account with API billing

That last point trips people up, so to be clear: Claude Code is not free. You sign in with either your Claude.ai subscription (flat monthly price, usage limits) or your Anthropic Console account (pay-as-you-go API pricing). For most individual developers, a subscription is the simpler and more predictable option.

Method 1: Install the VS Code Extension (Easiest)

Install the VS Code Extension (Easiest)

This is the fastest path in 2026.

1. Open VS Code
2. Go to the Extensions panel (Cmd+Shift+X on Mac, Ctrl+Shift+X on Windows/Linux)
3. Search for “Claude Code”
4. Install the official extension published by Anthropic
5. Click the Claude icon in the sidebar and sign in with your Claude account

That’s it. You’ll get a Claude panel inside VS Code where you can chat with the agent, watch it propose changes, and review diffs before accepting them.

Method 2: Install the CLI via npm

If you prefer the terminal (or want Claude Code available outside VS Code too):

npm install -g @anthropic-ai/claude-code

Then open your project in VS Code, open the integrated terminal (Ctrl+ ` ``), and run:

claude

On first run, it walks you through authentication in the browser. Once you’re signed in, you’re ready to go.

The nice part: when you run the CLI inside VS Code’s integrated terminal, it detects the editor and can show diffs in VS Code’s native diff viewer instead of raw terminal output. Best of both worlds.

Tip: Avoid installing with sudo. If you hit permission errors on Mac/Linux, fix your npm global directory instead — it saves you headaches later.

Signing In: Subscription vs API

When you first launch Claude Code, it asks how you want to authenticate:

Option A — Claude subscription (Pro/Max): Sign in with your Claude.ai account. You pay a flat monthly fee and get generous usage limits. This is what I’d recommend for most solo devs and indie hackers — predictable cost, no surprise bills.

Option B — Anthropic Console (API billing): Sign in with your Console account and pay per token. Makes sense for teams, CI pipelines, or if your usage is spiky.

You can check which account you’re using anytime with the /status command inside a session.

Your First Session: The Commands That Matter

Open your project folder in VS Code, launch Claude Code (extension panel or claude in the terminal), and try these:

1. /init — Create your CLAUDE.md

/init

This scans your project and generates a CLAUDE.md file — a project memory file that Claude reads at the start of every session. It captures your stack, conventions, build commands, and folder structure.

This single file is the highest-leverage thing you can set up. Edit it by hand and add things like:

# CLAUDE.md
- Stack: Next.js 15, TypeScript, Prisma, PostgreSQL
- Never write code comments
- Run `npm run typecheck` after every change
- API routes live in /app/api

Now every session starts with Claude already knowing your project’s rules.

2. Just describe the task

No special syntax needed. Type what you want like you’d tell a teammate:

Add rate limiting to the /api/generate endpoint. 
Use an in-memory store for now, 10 requests per minute per user.

Claude will read the relevant files, propose changes, and show you diffs. You approve or reject each edit.

3. Reference files with @

Refactor @src/services/billing.ts to extract the Stripe logic into its own module

The @ mention pulls that file directly into context so Claude doesn't have to search for it.

4. Use Plan Mode for bigger tasks

For anything non-trivial, ask Claude to plan first before touching code. In the terminal you can toggle planning behavior (Shift+Tab cycles modes in recent versions), or simply say:

Plan the implementation first. Don't write any code until I approve the plan.

Reviewing a plan takes 30 seconds. Reviewing a 15-file diff you didn’t expect takes 30 minutes.

Permissions: How Much Autonomy to Give It

By default, Claude Code asks before editing files or running commands. As you build trust, you can loosen this:

• Default mode — approves every action manually. Start here.
• Accept edits — auto-accepts file edits, still asks for shell commands.
• Full auto — Claude runs without asking. Only use this in projects under version control (which should be all of them).

The golden rule: commit before letting Claude loose. Git is your undo button.

Connecting MCP Servers (Optional, but Powerful)

Claude Code supports MCP (Model Context Protocol), which lets it talk to external tools — Linear, GitHub, databases, Sentry, whatever you use.

Example — adding Linear so Claude can read and update your issues:

claude mcp add --transport http linear https://mcp.linear.app/mcp

Once connected, you can say things like “pick up the next issue in my Linear backlog and implement it” and Claude handles the ticket-to-PR loop end to end.

Check your configured servers anytime with /mcp.

A Realistic Workflow (What Mine Looks Like)

Here’s the loop that works in practice:

1. Open the project, commit anything pending
2. Describe one task clearly — one feature or one bug, not five
3. Ask for a plan if the task touches more than 2–3 files
4. Review diffs as they come — don’t rubber-stamp
5. Make Claude verify its own work — “run the type checker and fix any errors”
6. Commit — you can even ask Claude to write the commit message

The developers getting the most out of Claude Code aren’t the ones giving it vague mega-prompts. They’re the ones giving it small, well-scoped tasks with clear success criteria — the same way you’d delegate to a junior engineer.

Common Issues and Fixes

“claude: command not found” — Your npm global bin isn’t on PATH. Run npm config get prefix and add its bin folder to your PATH, then restart the terminal.

Extension shows but won’t sign in — Sign out fully, restart VS Code, sign in again. Corporate proxies and VPNs are the usual suspects.

Diffs open in the terminal instead of VS Code — Make sure you’re running claude from VS Code's integrated terminal, not an external one, and that the extension is installed.

It keeps forgetting project conventions — You skipped /init. Create a CLAUDE.md. Seriously, this fixes 80% of "Claude did it wrong" complaints.

Usage limits hit too fast — Scope tasks tighter, use /compact to compress long sessions, and start fresh sessions for unrelated tasks instead of one endless conversation.

Final Thoughts

Setting up Claude Code in VS Code takes about five minutes. Learning to delegate to it well takes a couple of weeks — and that’s where the real productivity jump happens.

Start small: one bug fix, one refactor, one test file. Build the habit of writing clear task descriptions and reviewing diffs. Within a few sessions, you’ll wonder how you shipped without it.

Since the tooling moves fast, always cross-check details against the official docs:

• Claude Code docs: https://docs.claude.com/en/docs/claude-code/overview
• npm package: https://www.npmjs.com/package/@anthropic-ai/claude-code

Happy shipping. 🚀

If this helped, a clap or two goes a long way. I write about building and shipping software as a solo founder — follow for more practical dev guides.

Built with ☕ by Alishan — creator of AutoAIShorts, an AI tool that turns prompts into ready-to-post short videos in minutes.