Claude Code is primarily a command-line tool you run in your terminal, but with the VS Code extension and the JetBrains plugin you can use it right inside your usual code editor. You can chat while looking at your code, review Claude's proposed changes as diffs, and reference a selected range of code directly. This guide covers installation, sign-in, and the key features in both environments, based on the official documentation.
What is IDE integration?
You can use Claude Code in three main ways: the CLI (run with the claude command in a terminal), the VS Code extension, and the JetBrains plugin. All three share the same Claude account and the same core features — the real difference is simply where you chat. With IDE integration you never leave your editor: Claude automatically sees your open files and selection, and you review changes in the editor's diff view.
Before you start
- A paid Claude subscription (Pro, Max, Team, or Enterprise) or a Claude Console account. No API key is required — you sign in with this account the first time you open the extension or plugin.
- For VS Code, version 1.98.0 or higher.
- If you access Claude through a third-party provider such as Amazon Bedrock or Google Vertex AI, additional setup is required.
Install in VS Code
The VS Code extension bundles its own copy of the CLI for the chat panel, so you can start chatting as soon as the extension is installed.
- Install the extension — Find the 'Claude Code' extension in the VS Code Marketplace and install it.
- Sign in — The first time you open the panel, a sign-in screen appears. Click 'Sign in' and complete authorization in your browser.
- Send a prompt — Ask Claude to explain, debug, or change your code. Claude automatically sees your open files and selected code.
If the sign-in screen doesn't appear, reload the window from the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux) with 'Developer: Reload Window'. If you have ANTHROPIC_API_KEY set in your shell but still see the sign-in prompt, VS Code may not have inherited your shell environment — launch VS Code from a terminal with code ., or simply sign in with your Claude account.
What you can do in VS Code
Once the extension is installed, you get these features inside the editor:
- Review and edit plans — Review and adjust Claude's proposed plan before you accept it.
- Auto-accept edits — Optionally apply changes automatically as they're made.
- @-mention files — Reference a specific line range of selected code with
@. - History and multiple tabs — Run several conversations in separate tabs or windows.
- Rewind with checkpoints — Restore an earlier state easily.
- Manage plugins and marketplaces — Marketplaces you configure in the extension are shared with the CLI.
- Chrome automation (@browser) — Use
@browserto test locally running web apps and debug with console logs (requires the Claude in Chrome extension 1.0.36 or higher). - Connect external tools with MCP — Link external tools and data via MCP.
- Work with git — Create commits and pull requests, and run parallel tasks with git worktrees.
Install in JetBrains
JetBrains integrates through a dedicated plugin. It works with most JetBrains IDEs, including IntelliJ IDEA, PyCharm, Android Studio, WebStorm, PhpStorm, and GoLand.
- Install the 'Claude Code' plugin from the JetBrains Marketplace via Settings → Plugins.
- Launch it quickly with Cmd+Esc (or the IDE's run button).
The JetBrains plugin provides interactive diff viewing, sharing of your selected code (context), and more. For remote development, install the plugin on the remote host (not your local client). On WSL2, if you see 'No available IDEs detected', WSL2's NAT networking or the Windows Firewall is usually blocking the connection to the IDE — allowing WSL2 traffic through the firewall resolves it.
VS Code vs. JetBrains at a glance
| Item | VS Code extension | JetBrains plugin |
|---|---|---|
| Install from | VS Code Marketplace | Settings → Plugins |
| Quick launch | Panel · Command Palette | Cmd+Esc |
| Reviewing changes | Plan review + diff | Interactive diff |
| Bundled CLI | Chat CLI included | Not included |
| Requirement | VS Code 1.98.0+ | IntelliJ, PyCharm, etc. |
Extension/plugin vs. CLI — which to use
The VS Code extension bundles a CLI for the chat panel, so the extension alone is enough to chat. However, to run the claude command directly in VS Code's integrated terminal, you need to install the standalone CLI separately. In short: use the extension or plugin when you want to work visually inside your editor, and the CLI when your workflow centers on scripts, automation, or the terminal. They share the same account, settings, and marketplaces, so you can use both as needed.
FAQ
Do I really need an API key?
No. Sign in with a paid Claude subscription or a Claude Console account — no separate API key is required.
Does it work in Cursor or Windsurf?
These are editors built on VS Code. However, the official documentation explicitly covers VS Code and JetBrains; behavior in other editors is not confirmed by official sources. When unsure, check each editor's own guidance.