icaoberg / Connecting Claude AI to VSCode, including plugins

Anthropic does not currently ship an official Claude extension for VSCode, but there are several effective ways to bring Claude into your editor. This post walks through each approach, from the simplest to the most capable.

Option 1: Claude Code in the integrated terminal

The most direct path is Claude Code, Anthropic’s official CLI tool. Once installed, you run it inside VSCode’s integrated terminal (Ctrl+`` ) and it can read, edit, and create files in your workspace autonomously.

Installation

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

Then launch it from your project root:

claude

Claude Code is aware of your working directory and git state. You can ask it to fix a bug, write a test, refactor a function, or explain a file — and it will read the relevant code, make edits, and show you a diff before applying changes.

Why this works well with VSCode

VSCode’s integrated terminal keeps Claude Code running alongside your editor. You see file changes reflected immediately in the editor as Claude writes them. The combination feels natural: you review and navigate code in the editor while directing Claude through the terminal.

Option 2: Cline (community extension)

Cline is an open-source VSCode extension that brings an agentic AI assistant directly into the editor UI — no terminal required. It supports multiple model backends including Claude via the Anthropic API.

Installation

Search for Cline in the VSCode Extensions Marketplace (Ctrl+Shift+X) or install via the command line:

code --install-extension saoudrizwan.claude-dev

Configuration

After installing, open the Cline sidebar panel and enter your Anthropic API key under Settings. Select Claude Sonnet or Claude Opus as your model.

What Cline can do

• Read and write files anywhere in your workspace
• Run terminal commands on your behalf
• Browse the web to look up documentation
• Execute multi-step tasks end-to-end without leaving the editor

Cline is effectively Claude Code wrapped in a VSCode-native UI. It is a good choice if you prefer a chat panel over a terminal workflow.

Option 3: Continue (multi-model extension)

Continue is another popular open-source VSCode extension that supports Claude alongside other models (GPT-4o, Gemini, local Ollama models). It focuses on inline code completions and chat, rather than autonomous agentic tasks.

Installation

Search for Continue in the Extensions Marketplace, or:

code --install-extension continue.continue

Configuration

In ~/.continue/config.json, add Claude as a model:

{
  "models": [
    {
      "title": "Claude Sonnet",
      "provider": "anthropic",
      "model": "claude-sonnet-4-6",
      "apiKey": "your-anthropic-api-key"
    }
  ]
}

Continue adds an inline edit shortcut (Ctrl+I) and a chat sidebar. It is lighter than Cline — better suited for quick completions and targeted edits than full autonomous workflows.

Option 4: Cursor (Claude as the backend)

If you are open to switching editors, Cursor is a VSCode fork with Claude built in as a first-class model option. You select Claude Sonnet or Opus in the model picker and get the same familiar VSCode interface with deep AI integration — inline edit (Ctrl+K), multi-file Agent mode, and chat — all powered by Claude.

This is worth mentioning because Cursor installs all your existing VSCode extensions unchanged, so the migration cost is low.

Comparison

Which should you use?

• Just want to try Claude quickly: start with Claude Code in the terminal — zero configuration beyond installing the CLI.
• Prefer staying in the editor UI: install Cline from the marketplace and point it at your Anthropic API key.
• Want completions + lightweight chat: Continue is a good fit, especially if you also use other models.
• Willing to switch editors: Cursor gives the most polished experience with Claude as the backend.

All four approaches use the same Claude models under the hood. The difference is purely in how you interact with them.