Claude Code in VS Code vs JetBrains: integration comparison
Compare the VS Code extension and the JetBrains CLI-plus-plugin integration: what you install, where chat runs, setup order, and remote-host rules.
VS Code and Cursor use one extension that bundles the CLI. JetBrains uses a separate plugin that launches the CLI you install, so the two integrations share a settings file but not an install path. The source guides are Claude Code in VS Code and Claude Code in JetBrains.
Side by side
| VS Code / Cursor | JetBrains | |
|---|---|---|
| What you install | one extension that bundles the CLI | the CLI plus a plugin |
| Where the chat lives | a native panel inside the editor | the IDE terminal, with diffs rendered in the IDE |
| How it finds Claude | bundled binary | claude on PATH, or a path set in plugin settings |
| How it connects | extension process | plugin runs a local MCP server; the CLI connects over ws:// on a random loopback port |
| IDE requirement | VS Code 1.94.0 or later; Cursor on the same base | a current build of IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, GoLand, or Android Studio |
| Plugin channel | marketplace or Open VSX | JetBrains Marketplace, beta |
Setup order
VS Code or Cursor: install the extension, create an AWSQ or CCMAX key, write ~/.claude/settings.json, set claudeCode.disableLoginPrompt, then run /status and a short prompt. The extension bundles the CLI, so there is no separate CLI step unless you want terminal sessions or claude mcp add.
JetBrains: install the CLI first (npm install -g @anthropic-ai/claude-code), then the beta plugin, then set Settings → Tools → Claude Code [Beta] → Claude command. The plugin cannot launch a CLI it cannot resolve, and installing the plugin does not bundle one. Restart the IDE completely after installing the plugin; in Remote Development, install it on the host.
What stays the same
Both integrations use the same ~/.claude/settings.json with ANTHROPIC_BASE_URL, ANTHROPIC_AUTH_TOKEN, API_TIMEOUT_MS, and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC. Both accept an AWSQ or CCMAX key and the same Claude models. Both read the same base URL rule: use the bare host, because the client appends /v1/messages.
Remote development and containers
For VS Code Remote SSH, WSL, or a dev container, the settings file must be on the remote host at ~/.claude/settings.json. For JetBrains Remote Development, install the plugin on the host through Settings → Plugin (Host) and keep the CLI and settings file in the remote environment. A locally installed plugin will not connect to a remote project.
Troubleshooting differences
- VS Code or Cursor: a missing Spark icon usually means no file is open or VS Code is older than 1.94.0. A silent panel suggests the bundled CLI failed to launch; run Claude Code: Show Logs.
- JetBrains:
Cannot launch Claude Codemeansclaudeis not on the IDE'sPATH; set an absolute path ornpx @anthropic-ai/claude-code.No available IDEs detectedmeans the plugin is disabled, the IDE was not fully restarted, or the CLI is in another user session. - JetBrains diffs: if edits appear in the terminal instead of the IDE, set Diff tool to
autowith/configwhile connected. - Both: a 404 means the base URL includes
/v1; a 400 usually means the key belongs to another channel orsettings.jsonis malformed.
FAQ
Is the JetBrains integration a plugin-only install?
No. The plugin drives the claude command over a local socket, so the CLI must be installed and resolvable first. The VS Code and Cursor extension is the one that bundles the CLI.
Can I use the same key and settings file in both?
Yes. Both read ~/.claude/settings.json, and an AWSQ or CCMAX key works in either. The installations differ, not the account configuration.
Why is the JetBrains plugin beta?
The plugin is published as Claude Code [Beta] on the JetBrains Marketplace. Features and settings menus move between releases, so check the plugin page for the build you install.
Do I need an Anthropic account for either one?
No. ANTHROPIC_AUTH_TOKEN plus the AI in IDE base URL replaces the login prompt in both integrations.