How Claude Code works in JetBrains IDEs
Claude Code connects to JetBrains IDEs through an official plugin published on the JetBrains Marketplace. The official docs list IntelliJ IDEA, PyCharm, Android Studio, WebStorm, PhpStorm and GoLand, and say it works with most JetBrains IDEs. Once it is connected, Claude shows its proposed edits in the IDE's own diff viewer, sees the file or code you have selected, and can read the inspection warnings your IDE already shows, like lint and syntax errors.
The big difference from the Claude Code VS Code extension is how it is built. The VS Code extension gives you a chat panel with Claude Code bundled inside. The JetBrains plugin does not bundle anything. It runs the regular claude command in the IDE's integrated terminal and wires it into the editor. So you are using the same terminal Claude Code, with the IDE doing the parts it is good at: diffs, navigation and inspections.
How to install the Claude Code JetBrains plugin
- Install the Claude Code CLI first. The plugin needs the claude command on your PATH, and without it you get a "Cannot launch Claude Code" notification. Check it worked by running claude --version in any terminal.
- Install the plugin. In your IDE open Settings, then Plugins, then Marketplace, search for "Claude Code" and install the one published by Anthropic. Restart the IDE.
- Open your project from its root folder, so Claude sees the same files your IDE does.
- Open the IDE's integrated terminal and run claude. The first time, you are asked to log in. Any paid Claude plan (Pro, Max, Team or Enterprise) or a Claude Console account works, and you do not need an API key.
- Press Cmd+Esc (Mac) or Ctrl+Esc (Windows/Linux) from the editor, or click the Claude Code button, to jump straight to Claude from now on.
Not sure which plan to sign in with? Which Claude plan for Claude Code walks through it. On Windows, read Claude Code on Windows before you install the CLI.
What you get once it is connected
- Diffs in the IDE: proposed changes open in the JetBrains diff viewer instead of scrolling past in the terminal. You can switch this with the Diff tool setting in /config: auto shows diffs in the IDE, terminal keeps them in the terminal. That setting only appears while Claude Code is connected to the IDE.
- Selection context: the code you highlight, or the tab you have open, is shared with Claude automatically. Files blocked by a Read deny rule in your permissions are not shared.
- File references: Cmd+Option+K (Mac) or Alt+Ctrl+K (Windows/Linux) drops a precise reference like @src/auth.ts#L1-99 into your prompt.
- IDE diagnostics: Claude can read the lint and syntax errors your IDE's inspections already found. It asks for them when it needs them, not automatically after every edit, so if you want a check, tell it to look at the IDE's errors before it finishes.
The diagnostics part is the one I like most. JetBrains IDEs are strong at inspections, and letting Claude read those warnings directly beats copying error text into the chat. A prompt like "fix the change, then check the IDE errors for this file and clean up anything you introduced" puts that to work.
Fixes for the common snags
Common Claude Code JetBrains problems and fixes from the official docs
| Problem | Fix |
|---|---|
| "Cannot launch Claude Code" or "command not found" | The CLI is missing or not on the PATH your IDE sees. Run claude --version in a terminal, then set the full path under Settings, Tools, Claude Code [Beta], Claude command. |
| Esc does not stop Claude | Go to Settings, Tools, Terminal and untick "Move focus to the editor with Escape", or delete the "Switch focus to Editor" terminal shortcut. |
| /ide says "No available IDEs detected" | Check the plugin is installed and enabled, fully restart the IDE, and make sure you launched claude from the IDE's terminal or the project root. |
| Plugin features do not appear | Run Claude Code from the project root, confirm the plugin is enabled, and restart the IDE completely, sometimes more than once. |
| Using JetBrains Remote Development | Install the plugin on the remote host (Settings, Plugin (Host)), not on your local machine. |
| Using WSL2 on Windows | Set the Claude command to run through WSL, and if the IDE is not detected, allow WSL2 traffic through Windows Firewall or switch WSL2 to mirrored networking. |
On a Mac there is also an optional setting to use Option+Enter for new lines in your prompt. If the Option key starts behaving oddly in the terminal, that setting is the first thing to turn off.
One security setting to change
The official docs flag a specific risk for JetBrains users. In acceptEdits mode, and in auto mode, Claude can edit files in your project without asking, and that can include IDE configuration files your IDE runs automatically. In plain terms, an edit to one of those files could run commands without the usual permission prompt.
My recommendation: in a JetBrains IDE, use Manual mode for edits, so you approve each change in the diff viewer. You already have a good diff viewer open, so the cost is small. Claude Code permissions explained covers the modes, and Claude Code settings.json shows where to set them.
JetBrains plugin, VS Code extension or desktop app
Where to run Claude Code
| If you... | Use |
|---|---|
| Already work in IntelliJ, PyCharm, WebStorm or another JetBrains IDE | The JetBrains plugin |
| Already work in VS Code or Cursor | The VS Code extension |
| Are new to code and mostly describe what you want | The desktop app |
| Want the IDE's inspections to catch Claude's mistakes | The JetBrains plugin, with Manual mode |
My take: the JetBrains plugin is the most "terminal" of the editor options, because it really is the terminal Claude Code with the IDE plugged in. That suits people who already know their IDE well and want Claude to fit their workflow, not replace it. If that is not you, the desktop app is less to learn and does the same work. All of them share the same settings file, so moving between them later is easy.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
Is there an official Claude Code plugin for JetBrains?
Yes. Anthropic publishes the Claude Code plugin on the JetBrains Marketplace. It works with most JetBrains IDEs, including IntelliJ IDEA, PyCharm, Android Studio, WebStorm, PhpStorm and GoLand.
Do I need to install Claude Code separately for the JetBrains plugin?
Yes. The JetBrains plugin does not bundle Claude Code. Install the Claude Code CLI first so the claude command is on your PATH, then install the plugin and restart the IDE.
Do I need an API key to use Claude Code in IntelliJ or PyCharm?
No. Any paid Claude plan (Pro, Max, Team or Enterprise) or a Claude Console account works. You log in the first time you run claude.
How do I connect Claude Code to a JetBrains IDE from an outside terminal?
Start claude from your project root and run /ide. It connects to the running IDE, and if the plugin is missing it offers to install it and asks you to restart the IDE.
Why won't the Esc key stop Claude Code in the JetBrains terminal?
The IDE's terminal uses Esc to jump back to the editor. In Settings, Tools, Terminal, untick "Move focus to the editor with Escape" or remove the "Switch focus to Editor" shortcut.
Last reviewed by David Iya on October 11, 2026
