JetBrains IDEs - Claude Code Docs (original) (raw)

Claude Code integrates with JetBrains IDEs through a dedicated plugin, providing features like interactive diff viewing, selection context sharing, and more.

Supported IDEs

The Claude Code plugin works with most JetBrains IDEs, including:

Features

Installation

The plugin runs the claude 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:

If 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

Run claude 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:

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:

  1. Run claude
  2. Enter the /config command
  3. Set the diff tool to auto to show diffs in the IDE, or terminal to keep them in the terminal

Plugin settings

Configure the Claude Code plugin by going to Settings → Tools → Claude Code [Beta]:

General settings

ESC key configuration

If the ESC key doesn’t interrupt Claude Code operations in JetBrains terminals:

  1. Go to Settings → Tools → Terminal
  2. Either:
    • Uncheck “Move focus to the editor with Escape”, or
    • Click “Configure terminal keybindings” and delete the “Switch focus to Editor” shortcut
  3. Apply the changes

This allows the ESC key to properly interrupt Claude Code operations.

Special configurations

Remote development

The plugin must be installed on the remote host, not on your local client machine.

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.

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:

[wsl2]
networkingMode=mirrored

Then restart WSL with wsl --shutdown from PowerShell.

Troubleshooting

Plugin not working

If the plugin is installed but Claude Code features don’t appear in your IDE:

IDE not detected

If running claude shows “No available IDEs detected”:

Command not found

If clicking the Claude icon shows “command not found”:

  1. Verify Claude Code is installed by running claude --version in a terminal
  2. Configure the Claude command path in plugin settings
  3. For WSL users, use the WSL command format mentioned in the configuration section

Security considerations

When Claude Code runs in a JetBrains IDE with auto-edit permissions enabled, 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 auto-edit mode and allow bypassing Claude Code’s permission prompts for bash execution. When running in JetBrains IDEs, consider:

For Claude Code installation or login problems outside the IDE, see Troubleshoot installation and login.