Claude Code in JetBrains IDEs: IntelliJ, PyCharm, WebStorm and More
How to use Claude Code in IntelliJ IDEA, PyCharm, WebStorm, GoLand, PhpStorm and Android Studio: install the CLI and the plugin, connect with /ide, see diffs in the IDE's viewer, share selections and diagnostics, and fix the common Esc-key and WSL problems.
If you live in a JetBrains IDE, you don't have to switch editors to use Claude Code. Anthropic's Claude Code plugin connects the CLI to IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, GoLand, Android Studio and most other JetBrains IDEs.
Details as of October 2026, from Anthropic's JetBrains docs.
How it works
The plugin doesn't contain its own copy of Claude Code. It runs the claude command in your IDE's built-in terminal and connects to it. So you install two things:
- The Claude Code CLI. (How to Install Claude Code)
- The "Claude Code [Beta]" plugin from the JetBrains Marketplace, then restart the IDE.
You need a paid Claude plan (Pro, Max, Team or Enterprise) or a Claude Console account. You'll be asked to log in the first time claude runs.
What you get
- Quick launch:
Cmd+Esc(Mac) orCtrl+Esc(Windows/Linux) opens Claude Code from the editor. - Diffs in the IDE's diff viewer instead of the terminal.
- Selection context: whatever you've selected, or the open tab, is shared with Claude automatically.
- File references:
Cmd+Option+K(Mac) orAlt+Ctrl+K(Windows/Linux) inserts a reference like@src/auth.ts#L1-99. - Diagnostics: Claude can read the IDE's inspection results — lint and syntax errors — through a built-in tool.
Using it from another terminal
Prefer iTerm, Windows Terminal or another terminal app? Start Claude Code there and connect it:
claude
/ide
You'll see a message like Connected to IntelliJ IDEA. Start claude from the same directory as your IDE project so both see the same files.
To choose where diffs appear, run /config and set Diff tool to auto (IDE) or terminal.
Common problems
Esc doesn't stop Claude. JetBrains terminals grab the Esc key to move focus to the editor. Go to Settings → Tools → Terminal and untick "Move focus to the editor with Escape", or delete the "Switch focus to Editor" shortcut.
"Cannot launch Claude Code" / command not found. The IDE can't find claude on your PATH. Check claude --version in a terminal, then set the full path under Settings → Tools → Claude Code [Beta] → Claude command.
"No available IDEs detected" on WSL. WSL2's networking or Windows Firewall is blocking the connection. The simplest fix on Windows 11 is mirrored networking — add this to .wslconfig in your Windows user folder, then run wsl --shutdown:
[wsl2]
networkingMode=mirrored
For WSL, set the plugin's Claude command to wsl -d Ubuntu -- bash -lic "claude" (with your distribution's name). (Claude Code on Windows)
Remote Development. Install the plugin on the remote host (Settings → Plugin (Host)), not on your local machine.
A safety note
In acceptEdits or auto mode, Claude can change files without asking — and that includes IDE configuration files the IDE may execute. If you use those modes, keep an eye on what Claude edits, and prefer Manual mode on projects you don't fully trust. (Claude Code Permission Modes)
The summary
- Install the CLI, then the Claude Code plugin from the Marketplace.
- Run
claudein the IDE terminal, or/idefrom an external one. - Fix Esc in terminal settings; fix WSL with mirrored networking.
EasySpawn runs Claude Code on a persistent cloud server you can reach over SSH, so your IDE can connect to a workspace that keeps running after you close it. See how it works or join the waitlist.
Related: Claude Code in VS Code · Claude Code Keyboard Shortcuts · What Is an IDE? · Claude Code Tutorial for Beginners
Keep reading
Ultrathink in Claude Code: What It Does Now, and How Effort Levels Work
Ultrathink still works in Claude Code, but it no longer works the way old guides say — and "think hard" is no longer a keyword at all. How effort levels (low to max) actually control reasoning, how to set them with /effort, and when ultrathink is still worth typing.
Claude Code Output Styles: Concise, Explanatory, Learning and Your Own
Output styles change how Claude Code talks and works for a whole session: shorter answers, explanations of each change, or leaving pieces for you to write. The five built-in styles, how to switch with /output-style, and how to write a custom style file.