Claude Code VS Code Extension vs JetBrains Plugin
People think the VS Code extension and the JetBrains plugin work the same way. They do not. The VS Code extension brings its own copy of Claude Code and shows it in a side panel. The JetBrains plugin brings no copy. It runs the claude command you installed in the editor's terminal and links to it. So the JetBrains plugin will not start until Claude Code is installed on its own.
Claude Code VS Code Extension
Claude Code in a side panel of VS Code. You see each change and accept it.
The Claude Code VS Code extension puts Claude Code in a panel inside the VS Code editor. It shows planned changes as diffs you can accept or edit. You can point it at files and line ranges with an @ mention. It carries its own copy of Claude Code, so the panel works without the separate command line install. It also installs in Cursor, and you sign in with a Claude plan or a Console account.
Claude Code JetBrains Plugin
Links Claude Code to JetBrains IDEs. Changes open in the IDE's own diff viewer.
The Claude Code JetBrains plugin links Claude Code to IDEs like IntelliJ IDEA, PyCharm and WebStorm. It runs the claude command in the IDE's own terminal and connects to it. Changes then open in the IDE's diff viewer, not in the terminal. The file or lines you have selected are shared with Claude, and so are the IDE's error marks. The plugin does not carry Claude Code itself, so you install both.
In one line
- Claude Code VS Code Extension
- Claude Code in a side panel of VS Code. You see each change and accept it.
- Claude Code JetBrains Plugin
- Links Claude Code to JetBrains IDEs. Changes open in the IDE's own diff viewer.