Supported IDEs
The Claude Code plugin works with most JetBrains IDEs, including:- IntelliJ IDEA
- PyCharm
- Android Studio
- WebStorm
- PhpStorm
- GoLand
Features
- Quick launch: use
Cmd+Esc(Mac) orCtrl+Esc(Windows/Linux) to open Claude Code directly from your editor, or click the Claude Code button in the UI - Diff viewing: Claude Code opens code changes in the IDE diff viewer instead of the terminal; change this with the Diff tool setting in
/config - Selection context: the current selection or tab in the IDE is automatically shared with Claude Code.
Readdeny rules block this sharing for matching files - File reference shortcuts: use
Cmd+Option+K(Mac) orAlt+Ctrl+K(Linux/Windows) to insert file references such as@src/auth.ts#L1-99 - Diagnostic sharing: after Claude edits a file, Claude Code pulls the IDE’s new diagnostics for that file, such as lint and syntax errors, into the conversation, so Claude notices errors its edits introduce
Installation
The plugin runs theclaude command in your IDE’s integrated terminal and connects to it. It does not bundle its own copy of the CLI, so install both pieces:
1
Install the Claude Code CLI
Follow the quickstart to install the CLI if you haven’t already. The plugin shows a “Cannot launch Claude Code” notification when
claude isn’t on your PATH.2
Install the JetBrains plugin
Install the Claude Code plugin from the JetBrains Marketplace and restart your IDE.
claude is installed somewhere your IDE can’t find, set the full path in the plugin’s Claude command setting.
Claude Code works with any paid Claude subscription (Pro, Max, Team, or Enterprise) or a Claude Console account, and no API key is required. You’ll be prompted to log in the first time you run claude.
Usage
From your IDE
Runclaude from your IDE’s integrated terminal, and all integration features will be active.
From external terminals
Use the/ide command in any external terminal to connect Claude Code to your JetBrains IDE and activate all features:
Connected to IntelliJ IDEA. If Claude Code detects a running IDE that doesn’t have the plugin, /ide installs the plugin for you and asks you to restart the IDE.
If you want Claude to have access to the same files as your IDE, start Claude Code from the same directory as your IDE project root.
Configuration
Claude Code settings
Configure IDE integration through Claude Code’s settings:- Run
claude - Enter the
/configcommand - Set Diff tool to
autoto show diffs in the IDE, orterminalto keep them in the terminal
/config only when Claude Code is connected to the IDE, so run claude from the JetBrains terminal or run /ide first from an external terminal. See diffTool for the underlying setting.
Plugin settings
Configure the Claude Code plugin by going to Settings → Tools → Claude Code [Beta]:General settings
- Claude command: specify a custom command to run Claude, for example
claude,/usr/local/bin/claude, ornpx @anthropic-ai/claude-code - Suppress notification for Claude command not found: skip notifications about not finding the Claude command
- Enable using Option+Enter for multi-line prompts: on macOS only. When enabled, Option+Enter inserts new lines in Claude Code prompts. Disable if the Option key is being captured unexpectedly. Requires a terminal restart.
- Enable automatic updates: automatically check for and install plugin updates, applied on restart
ESC key configuration
If the ESC key doesn’t interrupt Claude Code operations in JetBrains terminals:- Go to Settings → Tools → Terminal
- Either:
- Uncheck “Move focus to the editor with Escape”, or
- Click “Configure terminal keybindings” and delete the “Switch focus to Editor” shortcut
- Apply the changes
Special configurations
Remote development
WSL configuration
If you’re using Claude Code on WSL2 with a JetBrains IDE and see “No available IDEs detected”, the cause is usually WSL2’s NAT networking or Windows Firewall blocking the connection between WSL2 and the IDE running on the Windows host. WSL1 uses the host’s network directly and isn’t affected.Allow WSL2 traffic through Windows Firewall
This is the recommended fix because it keeps your existing WSL2 networking mode.1
Find your WSL2 IP address
From inside your WSL shell, run:Note your subnet: take the first two segments of the address and follow them with
.0.0/16. For example, if the address is 172.21.123.45, your subnet is 172.21.0.0/16.2
Create a firewall rule
Open PowerShell as Administrator and run the following, adjusting the IP range to match your subnet:
3
Restart your IDE and Claude Code
Close and reopen both so the new rule takes effect.
Switch WSL2 to mirrored networking
Mirrored networking requires Windows 11 22H2 or later. If you’re on Windows 10, use the firewall rule above instead. Add this to.wslconfig in your Windows user directory:
wsl --shutdown from PowerShell.
Troubleshooting
Plugin not working
If the plugin is installed but Claude Code features don’t appear in your IDE:- Ensure you’re running Claude Code from the project root directory
- Check that the JetBrains plugin is enabled in the IDE settings
- Completely restart the IDE (you may need to do this multiple times)
- For Remote Development, ensure the plugin is installed in the remote host
IDE not detected
If the/ide command shows “No available IDEs detected”:
- Verify the plugin is installed and enabled
- Restart the IDE completely
- If you expected an automatic connection without running
/ide, check that you launchedclaudefrom the IDE’s integrated terminal - For WSL users, see WSL configuration above
Command not found
If clicking the Claude icon shows “command not found”:- Verify Claude Code is installed by running
claude --versionin a terminal - Configure the Claude command path in plugin settings
- For WSL users, use the WSL command format mentioned in the configuration section
Security considerations
When Claude Code runs in a JetBrains IDE inacceptEdits permission mode, it may be able to modify IDE configuration files that can be automatically executed by your IDE. This may increase the risk of running Claude Code in acceptEdits mode and allow bypassing Claude Code’s permission prompts for bash execution.
When running in JetBrains IDEs, consider:
- Using Manual mode for edits, because
acceptEditsand auto mode both approve edits inside your working directory without asking, except in