The VS Code extension
Install it by searching "Claude Code" in the Extensions view (Cmd+Shift+X), or open vscode:extension/anthropic.claude-code. The same extension works in both VS Code and Cursor — see the installation guide if you haven't set up the CLI yet.
The extension layers editor-native conveniences on top of the agent:
- Inline diffs — proposed changes highlighted in your editor before you accept
- @-mentions — reference files and folders with
@filenamein your prompt - Plan review — inspect Claude's plan in a visual panel before it executes
- Conversation history — browse and resume past sessions from the sidebar
- Multiple conversations — run parallel sessions for parallel tasks
- Terminal mode — drop to pure CLI without leaving the editor
- Chrome integration — enable browser automation from VS Code sessions
Configuration
Open Cmd+Shift+P → "Claude Code Settings" to tune the experience:
- Choose where Claude lives — sidebar, panel, or a new tab
- Configure preview servers for auto-verification of changes
- Manage plugin installation and marketplace connections
- Set keyboard shortcuts
VS Code vs. CLI
The extension and the terminal share one engine — pick based on the workflow, not on capability.
| When you want… | VS Code extension | CLI |
|---|---|---|
| Reviewing changes | Inline diff preview before accepting | Plain-text diffs in the terminal |
| Referencing files | @-mentions with autocomplete |
Type or paste paths manually |
| Session history | Browse and resume from the sidebar | --continue / --resume |
| Composition & scripting | Not the strength here | Pipes, non-interactive mode, shell integration |
Short version: use the extension when you want visual diff preview, @-mentions, and history in the sidebar. Use the CLI when you need pipe composition, non-interactive mode, custom shell integration, or you simply prefer the terminal.
The JetBrains plugin
Install from the JetBrains Marketplace by searching "Claude Code". It supports the full JetBrains family: IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, DataGrip, CLion, and AppCode.
- Interactive diff viewing — review before applying
- Selection context sharing — highlight code and ask Claude about it
- Remote development support via JetBrains Gateway
- WSL configuration for Windows users
WSL setup & common issues
On Windows with WSL, configure the networking mode so the IDE and the CLI can talk:
Settings → Claude Code → WSL2 networking mode: "mirrored"
Windows Firewall: Allow WSL2 traffic (see /en/jetbrains for firewall script)When the plugin misbehaves, the fix is almost always about PATH and where you launched from:
| Symptom | Fix |
|---|---|
| Plugin not working | Restart the IDE and confirm the Claude Code CLI is on your PATH |
| IDE not detected | Run Claude Code from inside the IDE's integrated terminal |
| Command not found | Configure PATH in the JetBrains shell settings |
The built-in IDE MCP server
The VS Code extension ships a built-in MCP server that gives Claude access to IDE features: file reference resolution, diff presentation, and terminal output. This is exactly why @file mentions work — they travel through the IDE MCP server, which resolves the path on the editor's behalf.
Security note: This MCP server only accepts connections from localhost, so the integration never exposes your editor to the network.
IDE Integration FAQ
How do you install the Claude Code VS Code extension?
Search "Claude Code" in the Extensions view (Cmd+Shift+X) or open vscode:extension/anthropic.claude-code. The same extension works in both VS Code and Cursor, and it adds inline diffs, @-mentions, plan review, conversation history, and a built-in terminal mode on top of the agent.
Should you use the Claude Code IDE extension or the CLI?
Both share one engine, so pick by workflow rather than capability. Use the extension when you want visual diff preview, @-mentions with autocomplete, and session history in the sidebar. Use the CLI when you need pipe composition, non-interactive mode, custom shell integration, or you simply prefer the terminal.
Which JetBrains IDEs does the Claude Code plugin support?
Install it from the JetBrains Marketplace by searching "Claude Code". It supports the full JetBrains family — IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, DataGrip, CLion, and AppCode — with interactive diff viewing, selection context sharing, remote development via JetBrains Gateway, and WSL configuration for Windows.
Why is the Claude Code IDE plugin not working?
Most IDE plugin issues are PATH-related. If the plugin is not working, restart the IDE and confirm the Claude Code CLI is on your PATH; if the IDE is not detected, run Claude Code from inside the IDE's integrated terminal; and if you get command not found, configure PATH in the JetBrains shell settings.
What is the built-in IDE MCP server in Claude Code?
The VS Code extension ships a built-in MCP server that gives Claude access to IDE features like file reference resolution, diff presentation, and terminal output — which is why @file mentions work. It only accepts connections from localhost, so the integration never exposes your editor to the network.
Quick summary
- The VS Code extension (also works in Cursor) adds inline diffs, @-mentions, and plan review
- Use the extension for visual review and history; use the CLI for piping and scripting
- The JetBrains plugin covers IntelliJ, PyCharm, WebStorm and more; most issues are PATH-related
- A localhost-only built-in IDE MCP server is what powers @file resolution and diff presentation