Two different integrations
The VS Code extension and the JetBrains plugin look similar from a distance but are built differently, and that decides how you install them:
| VS Code (and forks) | JetBrains IDEs | |
|---|---|---|
| What it is | An extension with its own chat panel | A plugin that connects the CLI to the IDE |
| Includes Claude Code | Yes, a bundled copy | No, install the CLI separately |
| Requirement | VS Code 1.94.0 or later | IntelliJ IDEA, PyCharm, Android Studio, WebStorm, PhpStorm, GoLand and most others |
| Where you type | The panel, or claude in the integrated terminal |
claude in the IDE terminal |
| Diffs | Inline, side by side, accept or reject per change | In the IDE’s own diff viewer |
| Open shortcut | Cmd+Esc / Ctrl+Esc toggles focus |
Cmd+Esc / Ctrl+Esc opens Claude Code |
| Insert file reference | Option+K / Alt+K |
Cmd+Option+K / Alt+Ctrl+K |
Both share ~/.claude/settings.json with the CLI, and the docs list the terminal, both IDE integrations and the desktop app as surfaces that read your organization’s managed settings.
Set up VS Code
- Install. Search “Claude Code” in the Extensions view, or open
vscode:extension/anthropic.claude-code. In Cursor usecursor:extension/anthropic.claude-code. It also installs in forks such as Kiro, and it is published on Open VSX. - Open the panel. Click the Spark icon in the editor toolbar, or run Claude Code: Open in New Tab from the Command Palette.
- Sign in with your Claude account or Console account.
- Pick a permission mode in the prompt box: Manual asks before edits and most shell commands, Plan proposes a plan you can comment on first, Edit automatically applies edits, and Auto lets a classifier review most actions.
What you get in the panel: your selection and open file go along as context, @ mentions files, folders and terminal output, and in Manual mode you see a side-by-side diff with Accept this change and Reject this change. Hover a message to rewind code, fork the conversation, or both. You can run several conversations in tabs, and the Web tab resumes cloud sessions from claude.ai. /mcp, /plugins and /usage work in the panel.
The extension supports a subset of the CLI’s commands. The ! shortcut for running a bash command and tab completion are CLI only. If you prefer the terminal look, set claudeCode.useTerminal to true, or just run claude in the integrated terminal; it connects to the editor and still shows diffs there.
Set up JetBrains
- Install the CLI first; see how to install Claude Code.
- Install the Claude Code plugin from the JetBrains Marketplace (listed as Claude Code [Beta]) and restart the IDE.
- Run
claudein the IDE’s integrated terminal. All integration features switch on. - From an external terminal, run
/ideinside Claude Code to connect. It confirms with a message such as “Connected to IntelliJ IDEA.” - Choose where diffs show with
/config, setting Diff tool toauto(IDE) orterminal.
Special cases from the docs:
- WSL: set the plugin’s Claude command to
wsl -d Ubuntu -- bash -lic "claude"with your distribution name. If/idesays “No available IDEs detected” on WSL 2, allow WSL traffic through the Windows Firewall or switch WSL 2 to mirrored networking. - Remote Development: install the plugin on the remote host, not on your local client.
- ESC does not interrupt: in Settings → Tools → Terminal, turn off “Move focus to the editor with Escape”.
The misunderstanding: “I installed the extension, so I have Claude Code”
In VS Code you do, but only inside VS Code: the extension does not add claude to your PATH, so a terminal elsewhere will not find it. In JetBrains it is the other way round: the plugin alone does nothing until the CLI is installed. A second point people miss: the JetBrains docs warn that in auto-approve edit modes Claude could change IDE configuration files that the IDE runs automatically, and suggest Manual mode for edits.
What this means for a team
Because the extension, the plugin and the CLI read the same settings files, a committed .claude/settings.json with permissions and hooks behaves the same whether a developer prefers VS Code, IntelliJ or the terminal. What does not travel is what each developer’s sessions learned along the way. If part of the team works in Cursor’s own agent instead, see Claude Code vs Cursor and shared memory across coding agents.
Where Bombos fits
The editor decides where you see Claude’s work; it does not decide what Claude knows about your team. Bombos is a plugin that gives Claude Code in any editor, and the team’s other AI tools, one shared memory with team knowledge, learned rules and what sits in mail, documents and repos, traceable to the source. One developer can try it on their own setup first.
Related questions
Does Claude Code work in Cursor?
Yes. The VS Code extension installs in Cursor and other forks, and is also published on Open VSX.
Do I need an API key for the extension?
No. Any paid Claude plan (Pro, Max, Ultra, Team or Enterprise) or a Console account works. Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry are supported too.
Can I continue a VS Code conversation in the terminal?
Yes. The extension and the CLI share conversation history; run claude --resume in a terminal to pick it up.
Why does the JetBrains plugin say Cannot launch Claude Code?
The plugin does not include Claude Code itself. Install the CLI, or set the full path in the plugin's Claude command setting.
Can I use the terminal interface inside VS Code instead of the panel?
Yes. Set claudeCode.useTerminal to true, or run claude in the integrated terminal, where it connects to the editor automatically.
