Pick the one that matches how you already work
Claude Code is not a code editor. It is an assistant that reads your project, makes changes and runs commands, and it can live in four places. They run the same Claude Code underneath; Anthropic's desktop documentation says the app “runs the same underlying engine with a graphical interface.” So the best IDE for Claude Code is the one you will actually open every day.
| If you… | Use | Terminal needed? |
|---|---|---|
| Have never used a terminal and do not want to | The Claude desktop app, Code tab | No |
| Already work in VS Code, Cursor or another VS Code-based editor | The Claude Code extension | No |
| Work in IntelliJ, PyCharm, WebStorm or another JetBrains IDE | The JetBrains plugin plus the command-line tool | Yes, inside the IDE |
| Want scripts, automation or several sessions side by side, or use any other editor | The terminal (the claude command) | Yes |
Every option needs a paid account. Anthropic's setup page: “Claude Code requires a Pro, Max, Team, Enterprise, or Console account. The free claude.ai plan does not include Claude Code access.”
No terminal: the Claude desktop app
Anthropic's setup page puts it first for anyone who would rather not type commands: “Prefer a graphical interface? The Desktop app lets you use Claude Code without the terminal.” It runs on macOS, Windows (x64, with a separate ARM64 installer) and, in beta, Linux.
- Download the Claude app from claude.com/download and install it.
- “After installing, launch Claude, sign in, and click the Code tab.” (Anthropic's desktop documentation.)
- Choose the folder you want Claude to work in, type what you want done and press Enter.
What you get that a chat window does not have: a diff view to “review modifications file by file,” several sessions in parallel (Cmd+N on macOS, Ctrl+N on Windows), and, for folders tracked with Git, an option to give each session “its own isolated copy of your project using Git worktrees.”
VS Code, Cursor and other VS Code-based editors: the extension
Anthropic's VS Code documentation calls the extension “the recommended way to use Claude Code in VS Code.” You need VS Code 1.94.0 or later.
- Press Cmd+Shift+X (Mac) or Ctrl+Shift+X (Windows/Linux) to open the Extensions view, search for Claude Code, and click Install.
- Open any file and click the Spark icon at the top right of the editor, or click ✻ Claude Code in the status bar at the bottom right.
- Click Sign in and finish in your browser. No API key is needed.
The same extension installs in Cursor and other VS Code-based editors; the docs point those editors to the Open VSX listing. When we read that listing on 2026-10-13 it showed “Claude Code for VS Code” version 2.1.296, requiring VS Code 1.94.0 or later, the same version number as the command-line tool on our machine.
Two things the docs say that save confusion later:
- The extension carries its own copy of Claude Code. Installing it “does not put
claudeon your shell PATH,” so typingclaudein VS Code's terminal needs the separate install in Option 4. - A few things are terminal-only. The extension shows a subset of commands and skills, and has no
!shell shortcut and no tab completion. Everything else you are likely to need, including plan review, @-mentions of files and rewinding Claude's edits, is in the panel.
JetBrains IDEs: the plugin plus the command-line tool
The JetBrains documentation lists IntelliJ IDEA, PyCharm, Android Studio, WebStorm, PhpStorm and GoLand. Unlike the VS Code extension, the plugin “does not bundle its own copy of the CLI, so install both pieces”:
- Install the command-line tool (Option 4 below).
- Install the plugin from the JetBrains Marketplace (it was listed as Claude Code [Beta], plugin 27310, when we checked on 2026-10-13) and restart the IDE.
- Run
claudein the IDE's built-in terminal, or press Cmd+Esc (Mac) / Ctrl+Esc (Windows/Linux). Claude's changes then open in the IDE's own diff viewer.
The docs warn that in auto-accept mode Claude Code “may be able to modify IDE configuration files that can be automatically executed by your IDE,” and suggest manual approval of edits. The same warning appears for VS Code. Approve edits one at a time until you trust the setup.
Any editor: the terminal
The command-line tool works with every editor, because it does not live in one: the docs say “The CLI works in any terminal.” Use it alongside Zed, Sublime Text, Vim or nothing at all. Install it with the command for your system from Anthropic's setup page:
curl -fsSL https://claude.ai/install.sh | bash
irm https://claude.ai/install.ps1 | iex
Then open a new terminal window and check it worked. This is what our machine printed on 2026-10-13:
claude --version 2.1.296 (Claude Code)
If you started claude in a separate terminal and want it to use VS Code's or a JetBrains IDE's diff viewer, type /ide inside Claude Code to connect them. If anything looks wrong, claude doctor prints read-only installation and settings diagnostics.
You can switch later without starting over
- Settings are shared. The VS Code docs say
~/.claude/settings.jsonis “shared between the extension and CLI”, including allowed commands, hooks and MCP servers. - Conversations are shared. “The extension and CLI share the same conversation history.” Run
claude --resumein a terminal to pick up a conversation you started in the panel. - Your project's instructions travel with the folder. The
CLAUDE.mdfile in your project is what Claude reads at the start of every session, whichever of the four places you open it from. Writing a good one matters more than which window you use.
This guide is free and complete. Brainfile is the memory around it.
Nothing on this page is part of Brainfile. Every option above works without it. Brainfile is a set of files for your project folder, which all four of them read.
Brainfile is a set of files that gives Claude Code a working memory of your project and your rules, so you stop re-explaining yourself every session. The free 30-day trial pulls the Basic set into your project: the Autopilot protocol, 10 pattern files and the weekly freshness feed. No card to start, and the files you pull stay yours.
Frequently Asked Questions
What is the best IDE for Claude Code?
The one you already use. Claude Code runs as an extension in VS Code and VS Code-based editors such as Cursor, as a plugin in JetBrains IDEs, inside the Claude desktop app, or in any terminal next to any editor. If you have never used a terminal, start with the desktop app's Code tab.
Is Claude Code a code editor?
No. Claude Code is an assistant that reads your project, edits files and runs commands. You review its changes in an editor or in the desktop app's diff view.
Does Claude Code work in Cursor?
Yes. Anthropic's VS Code documentation links a direct install for Cursor, and other VS Code-based editors can install the same extension from the Open VSX registry.
Can I use Claude Code without the terminal?
Yes. Anthropic's setup page says the Desktop app lets you use Claude Code without the terminal. The VS Code extension also works without typing commands.
Do I need a paid plan for Claude Code?
Yes. Anthropic's setup page says Claude Code requires a Pro, Max, Team, Enterprise or Console account, and that the free claude.ai plan does not include Claude Code access.