JetBrains IDEs changedjetbrains
Nearest release: v2.1.296, published 3 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Oct 2026 20:45 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+37added
Lines−45removed
From line
27
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 27, old and new numbered
/
from line 27
2727
2828The 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:
2929
30<Steps>
31 <Step title="Install the Claude Code CLI">
32 Follow the [quickstart](/docs/en/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.
33 </Step>
30**1. Install the Claude Code CLI**
3431
35 <Step title="Install the JetBrains plugin">
36 Install the [Claude Code plugin](https://plugins.jetbrains.com/plugin/27310-claude-code-beta-) from the JetBrains Marketplace and restart your IDE.
37 </Step>
38</Steps>
32Follow the [quickstart](/docs/en/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.
3933
34**2. Install the JetBrains plugin**
35
36Install the [Claude Code plugin](https://plugins.jetbrains.com/plugin/27310-claude-code-beta-) from the JetBrains Marketplace and restart your IDE.
37
4038If `claude` is installed somewhere your IDE can't find, set the full path in the plugin's [Claude command setting](#general-settings).
4139
4240Claude 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](/docs/en/authentication#log-in-to-claude-code) the first time you run `claude`.
from line 41
4341
4442## Usage
4543
46<span id="from-your-ide" />
47
4844### Run Claude Code from your IDE
4945
5046Run `claude` from your IDE's integrated terminal, and all integration features will be active.
5147
52<span id="from-external-terminals" />
53
5448### Connect from an external terminal
5549
5650Use the `/ide` command in any external terminal to connect Claude Code to your JetBrains IDE and activate all features:
from line 84
9084* **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.
9185* **Enable automatic updates**: automatically check for and install plugin updates, applied on restart
9286
93<Tip>
94 For WSL users: Set `wsl -d Ubuntu -- bash -lic "claude"` as your Claude command (replace `Ubuntu` with your WSL distribution name)
95</Tip>
87> [!TIP]
88>
89> For WSL users: Set `wsl -d Ubuntu -- bash -lic "claude"` as your Claude command (replace `Ubuntu` with your WSL distribution name)
9690
9791#### ESC key configuration
9892
from line 104
110104
111105### Remote development
112106
113<Warning>
114 When using JetBrains Remote Development, you must install the plugin on the remote host via **Settings → Plugin (Host)**, not on your local client machine.
115</Warning>
107> [!WARNING]
108>
109> When using JetBrains Remote Development, you must install the plugin on the remote host via **Settings → Plugin (Host)**, not on your local client machine.
116110
117111### WSL configuration
118112
from line 116
122116
123117This is the recommended fix because it keeps your existing WSL2 networking mode.
124118
125<Steps>
126 <Step title="Find your WSL2 IP address">
127 From inside your WSL shell, run:
119**1. Find your WSL2 IP address**
128120
129 ```bash theme={null}
130 hostname -I
131 ```
121From inside your WSL shell, run:
132122
133 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`.
134 </Step>
123```bash theme={null}
124hostname -I
125```
135126
136 <Step title="Create a firewall rule">
137 Open PowerShell as Administrator and run the following, adjusting the IP range to match your subnet:
127Note 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`.
138128
139 ```powershell theme={null}
140 New-NetFirewallRule -DisplayName "Allow WSL2 Internal Traffic" -Direction Inbound -Protocol TCP -Action Allow -RemoteAddress 172.21.0.0/16 -LocalAddress 172.21.0.0/16
141 ```
142 </Step>
129**2. Create a firewall rule**
143130
144 <Step title="Restart your IDE and Claude Code">
145 Close and reopen both so the new rule takes effect.
146 </Step>
147</Steps>
131Open PowerShell as Administrator and run the following, adjusting the IP range to match your subnet:
148132
133```powershell theme={null}
134New-NetFirewallRule -DisplayName "Allow WSL2 Internal Traffic" -Direction Inbound -Protocol TCP -Action Allow -RemoteAddress 172.21.0.0/16 -LocalAddress 172.21.0.0/16
135```
136
137**3. Restart your IDE and Claude Code**
138
139Close and reopen both so the new rule takes effect.
140
149141#### Switch WSL2 to mirrored networking
150142
151143Mirrored networking requires Windows 11 22H2 or later. If you're on Windows 10, use the firewall rule above instead.
from line 215
223215
224216**Listening interface.** Which network interface the server binds to is controlled by **Accept connections from all network interfaces** under **Settings → Tools → Claude Code \[Beta] → Networking (Advanced)**. With the setting disabled, the server listens on `127.0.0.1` only and is not reachable from other hosts. With it enabled, the port is reachable from your local network. The setting exists for cases where the CLI cannot reach the IDE over loopback, such as WSL2 with default NAT networking or a remote-IDE setup; see [WSL configuration](#wsl-configuration) for that scenario.
225217
226<Warning>
227 Enabling **Accept connections from all network interfaces** makes the IDE MCP port reachable from your local network. Connections still require the auth token from the lock file, but because the transport is unencrypted `ws://`, both the session traffic and that token cross the network in cleartext when the setting is on. Only turn it on when loopback can't work. For WSL2, prefer [mirrored networking](#switch-wsl2-to-mirrored-networking) so the Windows loopback interface is shared with the Linux VM and the socket can stay on loopback.
228</Warning>
218> [!WARNING]
219>
220> Enabling **Accept connections from all network interfaces** makes the IDE MCP port reachable from your local network. Connections still require the auth token from the lock file, but because the transport is unencrypted `ws://`, both the session traffic and that token cross the network in cleartext when the setting is on. Only turn it on when loopback can't work. For WSL2, prefer [mirrored networking](#switch-wsl2-to-mirrored-networking) so the Windows loopback interface is shared with the Linux VM and the socket can stay on loopback.
229221
No line in this hunk matches that.