OmniscioGuidesClaude Code in JetBrains
Claude Code JetBrains plugin not working
The JetBrains plugin puts Claude Code inside IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, GoLand and Android Studio. It is a different shape from the VS Code extension: it runs your own claude command in the IDE's terminal and talks to the IDE from there. The reports this page covers come back to that difference.
Checked against Anthropic's documentation on November 16, 2026, with the changelog's newest release at 2.1.325. No IDE was run on our side for this page. By the Omniscio team. Updated .
Start here
Five moves are worth making, and they go in this order:
- Check the CLI is installed and current. Run
claude --versionin a terminal, thenclaude update. - Find where
claudelives. Runwhich -a claudeon macOS or Linux, orwhere.exe claudein PowerShell on Windows, and copy the path it prints. If it prints nothing, noclaudeis on your PATH yet. - Paste that path into the plugin. Settings → Tools → Claude Code [Beta] → Claude command. When
claudelives inside WSL, the WSL command form further down replaces the path. - Completely restart the IDE, then run
claudefrom the IDE's own integrated terminal, or run/idefrom an outside one. - On Windows with WSL2, let WSL2 reach the IDE through Windows Firewall, as the WSL2 section below sets out.
The rest of this page explains why each one matters, and what to do when one of them does not settle it.
What the plugin actually is
The plugin does not draw a chat window of its own. It runs the claude command in the IDE's integrated terminal and connects to it, and the features arrive in that terminal session.
It also does not bundle a copy of the CLI. That is the opposite of the VS Code extension, which ships its own copy for its panel. So on JetBrains there are two pieces to install, and only one of them is the plugin.
Install the CLI first, then install the Claude Code plugin from the JetBrains Marketplace and restart the IDE. Anthropic notes the Marketplace is third-party software it does not endorse, maintain or audit.
What the terminal session then gets you is integration, not a panel: diffs open in the IDE's own diff viewer, your selection travels with the prompt, and the Diff tool entry appears in /config only once the CLI is connected. See the VS Code guide's note on JetBrains for the same point from the other side.
"Cannot launch Claude Code"
Anthropic gives one documented cause: the plugin runs your installed claude, and it shows this notice "when claude isn't on your PATH". A WSL2 setup can raise the same notice for a different reason, covered further down.
The fix is the plugin's own setting, not your shell. Open Settings → Tools → Claude Code [Beta] and set Claude command to the full path. Anthropic's own examples run from a bare command to a full path: claude, /usr/local/bin/claude and npx @anthropic-ai/claude-code.
On WSL the command has to be the WSL form. Anthropic's tip is wsl -d Ubuntu -- bash -lic "claude", with your own distribution name in place of Ubuntu. The -lic matters: it makes the shell load your login profile, so PATH is set up the way it is in your terminal.
Leave the Suppress notification for when Claude Command is not found switch beside it off while you are diagnosing, so the notice keeps telling you. Then check claude --version in a terminal outside the IDE.
"No available IDEs detected"
This is the line /ide prints when the running CLI cannot find the plugin to attach to. Anthropic gives three checks, and they run in this order:
- Verify the plugin is installed and enabled, in the IDE settings rather than only in the Marketplace.
- Restart the IDE completely. Not a window reload: close the whole IDE and open it again.
- If you expected a connection without running
/ide, check that you launchedclaudefrom the IDE's integrated terminal. A CLI started outside the IDE detects nothing unless you run/idein it.
Two things outside the plugin break this too. Claude Code has to be running from the project root, and in Remote Development the plugin must be installed on the remote host through Settings → Plugin (Host), not on your local machine.
If your IDE is on Windows and your claude is inside WSL2, the next section is the one you want.
The plugin is installed but the features are missing
Anthropic's list for this state is short, and the third item is the one worth doing twice:
- Run Claude Code from the project root directory, so it has the same files the IDE has open.
- Check that the plugin is enabled in the IDE's settings, not merely installed.
- Completely restart the IDE, and expect to do it more than once. Anthropic says "you may need to do this multiple times".
- In Remote Development, install the plugin on the remote host.
One more thing to check before you call a feature missing: the Diff tool entry exists in /config only while the CLI is connected to the IDE. Run claude from the IDE's terminal, or run /ide first from an external terminal, and it appears.
The features worth checking for once it is connected: your selection and open file travel with each prompt, Cmd+Option+K or Alt+Ctrl+K inserts a file reference like @src/auth.ts#L1-99, and Claude can read the IDE's inspection diagnostics through the getDiagnostics tool. The transcript shows ⧉ Selected N lines from <file> when the selection travels.
WSL2: Claude starts but never connects
Anthropic names two causes for this on WSL2: the virtual machine's NAT networking, or Windows Firewall, blocking the connection between WSL2 and the IDE running on Windows. WSL1 uses the host's network directly and is not affected.
The recommended fix is a firewall rule, because it keeps your existing networking mode. Run hostname -I inside WSL, take the first two segments of the address and follow them with .0.0/16, so 172.21.123.45 gives the subnet 172.21.0.0/16. Then open PowerShell as Administrator and run this with your own range:
New-NetFirewallRule -DisplayName "Allow WSL2 Internal Traffic" -Direction Inbound -Protocol TCP -Action Allow -RemoteAddress 172.21.0.0/16 -LocalAddress 172.21.0.0/16Close and reopen both the IDE and Claude Code so the rule takes effect.
The other road is mirrored networking, which needs Windows 11 22H2 or later. Add networkingMode=mirrored under [wsl2] in .wslconfig in your Windows user directory, then run wsl --shutdown from PowerShell. On Windows 10, use the firewall rule instead.
WSL2 can also fail for a reason that has nothing to do with the firewall. If the IDE's terminal shell is set to WSL and Claude is installed inside WSL, an open report shows the plugin writing its lock file to the Windows profile's .claude\ide.
The WSL copy of Claude looks only in the Linux ~/.claude/ide, so it never finds the lock file. The session starts and never attaches, and what you see is the misleading "Cannot launch Claude Code" notice.
The shortcut that does not do what you expect
If Esc will not interrupt Claude Code in the JetBrains terminal, the IDE is taking the key first. Go to Settings → Tools → Terminal and either uncheck Move focus to the editor with Escape, or click Configure terminal keybindings and delete the Switch focus to Editor shortcut. Apply, then try again.
Two other plugin settings are worth a look while you are in there. Enable using Option+Enter for multi-line prompts is macOS only and needs a terminal restart. Enable automatic updates applies plugin updates on restart, which is why an update lands the next time you reopen the IDE.
Sign-in and credentials inside the IDE
Claude Code works with any paid Claude subscription (Pro, Max, Ultra, Team or Enterprise) or a Claude Console account, and no API key is required. You are asked to log in the first time you run claude.
If credentials work in your terminal but not in the IDE, the cause Anthropic names is inheritance: the IDE process did not pick up your shell environment. Set the provider environment variables in the IDE's own settings, or launch the IDE from a terminal where they are already exported.
If clicking the Claude icon answers with command not found, that is the CLI missing or the plugin's command path being wrong, not a sign-in fault. Check claude --version in a terminal, then set the command path as above.
Why there is no chat panel like VS Code's
The request to add a graphical chat panel is open on Anthropic's tracker as we write, and the reporter's words are that "a terminal tab is not enough".
Anthropic has not shipped one. The plugin's documented design is still the integrated terminal, which is why the same Claude Code looks richer in VS Code: that extension bundles its own CLI and draws its own panel. On JetBrains you get the CLI, in your IDE's terminal, with the IDE's diff viewer wired in.
If you want the panel, the VS Code route is a separate install with its own failure modes. Our Claude Code not working in VS Code guide covers those, including the blank panel and the WSL bug behind it.
Known bugs, and the versions that fixed some
Several JetBrains faults are already fixed, so check your version before troubleshooting them. 2.1.132 fixed scroll-wheel handling in 2025.2 terminals, and 2.1.136 fixed MCP servers from .mcp.json vanishing after /clear.
2.1.160 removed the JetBrains plugin install suggestion from startup, 2.1.166 fixed terminal flicker on 2026.1 and later, and 2.1.239 fixed Edit and Write calls pausing for about five seconds. 2.1.311 fixed /ide claiming it had installed the plugin when nothing was installed.
These four are reports from users, not documented behaviour. Each was open when we read the tracker on November 16, 2026.
- A Write approved in the diff view loses the file's final newline, while a Write that needs no approval keeps it.
- The plugin ignores the
modelinsettings.jsonand starts on a Bedrock model, which fails with a 403 on restricted IAM. - The tab opened by the toolbar button keeps the title "Claude Code" instead of following the session, and dictation apps cannot paste into it.
- Remote Development through a devcontainer reports no available IDEs while selection sharing stays dead.
If you have not run claude update yet, that is still the first thing to try.
Two security notes from Anthropic's own page
In acceptEdits permission mode, Claude Code in a JetBrains IDE may be able to modify IDE configuration files that the IDE then executes. Anthropic's advice is to use Manual mode for edits and be aware of which files Claude can reach.
The plugin's MCP server listens on an OS-assigned port over unencrypted ws://, with a token in a lock file the CLI must present. Accept connections from all network interfaces makes that port reachable from your local network, and with it both the traffic and the token cross in cleartext. Leave it off unless loopback genuinely cannot work.
Worth knowing if your organization allowlists MCP tools: the server is named ide, is hidden from /mcp, and exposes exactly one tool to the model, the read-only mcp__ide__getDiagnostics. The JetBrains plugin exposes no code-execution tool.
Does Omniscio fix any of this?
No. Omniscio is a standalone desktop application for running several agent sessions side by side, and its build produces desktop installers for Windows, macOS and Linux only. It ships no JetBrains, IntelliJ or VS Code plugin, so installing it cannot make a plugin connect.
One thing it does touch is the CLI. First-run setup offers to install Claude Code, trying Anthropic's native installer first, then npm, then winget on Windows. That puts a claude where Omniscio can spawn it. It does not add anything to the PATH your IDE reads.
If what you actually want is to watch the work rather than the terminal: its diff viewer is built on Monaco, the engine VS Code uses, so a diff there looks like the one you know. The features page lists the rest, the pricing page has the plans, and the download page has the installers.
Sources
- JetBrains IDEs: the plugin's design, the two pieces to install, every settings entry, the WSL2 networking fixes, the troubleshooting list and the security notes. Read November 16, 2026.
- Troubleshoot installation and login: the IDE environment-inheritance note. Read November 16, 2026.
- Claude Code changelog: every version number on this page, newest release 2.1.325 on November 13, 2026. Read November 16, 2026.
- Reports in Anthropic's issue tracker, read November 16, 2026: #96790, #101164, #97755, #106898, #107723, #104508, #104282, #31938 and #22549.
Two GitHub issues are often cited for this problem: #31938 and #22549. Both were closed as duplicates by a bot, with no answer in them. #31938 describes the "Cannot launch Claude Code" plus "No available IDEs detected" pair this page covers; #22549 is a Rider report of IDE detection failing.
Omniscio's own source, and its first-run and startup fixes page and diff viewer page, for what this page says about this app.
Common questions
Why is there no Claude Code panel in IntelliJ, PyCharm or WebStorm?
Because the JetBrains plugin has no chat panel. It runs the claude command in the IDE's integrated terminal and connects to it, so the Claude Code button gives you a terminal tab, not a chat window. The VS Code extension draws its own panel; a request for one in JetBrains is open on Anthropic's tracker.
What does Cannot launch Claude Code mean?
The plugin runs your installed claude command, because it does not bundle a copy of the CLI. Anthropic's documentation says the notification appears when claude is not on your PATH. If claude lives somewhere your IDE cannot see, put the full path in the plugin's Claude command setting under Settings → Tools → Claude Code [Beta].
Why does /ide say No available IDEs detected when my IDE is open?
Anthropic's checks are that the plugin is installed and enabled, that the IDE has been restarted completely, and, if you expected a connection without running /ide, that you launched claude from the IDE's integrated terminal. In Remote Development the plugin has to be installed on the remote host. On WSL2 the likely cause is networking, covered further down the page.
Can I use my Pro subscription in the JetBrains plugin?
Yes. Anthropic's page says Claude Code works with any paid Claude subscription, Pro, Max, Ultra, Team or Enterprise, or with a Claude Console account, and that no API key is required. You are asked to log in the first time you run claude, in the IDE's terminal.
Does Omniscio have a JetBrains plugin?
No. Omniscio is a standalone desktop application for running several agent sessions side by side, and it builds desktop installers for Windows, macOS and Linux only. Installing it cannot make a JetBrains plugin connect. It can install the Claude Code CLI for its own sessions, which is a separate thing from the claude your IDE has to find.
Stop juggling terminals
Omniscio runs several agent sessions side by side in one window, each with its own context and its own diff view. Any model, any harness — Claude Code, Codex, OpenCode, Devin, Pi, and Hermes all supported.