Claude Code started life as a terminal tool. It still is one. But there are now official extensions for VS Code and JetBrains, and for most developers the IDE version is the better starting point.
An IDE is an Integrated Development Environment. That is the long name for a code editor that bundles everything a developer juggles into one window: the file tree on the side, the editor in the middle, a built-in terminal at the bottom, and tools for running and debugging the code. Think of it like a kitchen workstation where the chopping board, the stove, and the spice rack are all within arm's reach. VS Code and the JetBrains family (IntelliJ, PyCharm, WebStorm) are the two most common IDEs. An extension is a small add-on that adds new features to one of these editors, the way an app adds new features to your phone.
The reason to install the Claude Code extension is friction. In the terminal, you tell Claude which file to look at. In the IDE, Claude already knows which file is open and which lines are highlighted. The context is shared without you typing a path.
This page covers what the extensions give you, how to install them, and when the terminal is still the right choice.
The features on top of the terminal version split roughly into four buckets.
Context sharing. Claude reads the currently open file, the cursor position, and any selection. You can also attach a specific file or range of lines by typing @ followed by the filename, the same @ shape used to tag people in chat apps. No more pasting paths into the chat.
Native diff view. When Claude proposes changes, they open in the editor's native diff tool. A diff is a side-by-side view of two versions of a file: the old version on the left, the new version on the right, with the differences highlighted. Line by line, you accept or reject the change. It is the same view you use when reviewing other people's code.
Checkpoints (VS Code extension). The VS Code extension tracks the state of your files at each step and lets you rewind from a button on any message. Made a mistake five turns ago? Rewind. Want to fork a conversation and try two approaches? Branch from the checkpoint. The terminal CLI has the same rewind built in: press Esc twice on an empty prompt. The JetBrains plugin does not have the graphical version yet, so JetBrains users run the CLI in the integrated terminal for rewind, or rely on git.
Conversation tabs. Multiple Claude conversations open at once, each in its own tab. Imagine you are refactoring a database module in one tab while asking Claude to explain a bug in a separate component in another tab. The two conversations stay independent. They do not share context with each other, so there is no risk of them getting confused about which code you mean.
Info
Tip: Selection-as-context is the killer feature. Highlight a function, ask "why is this slow," and Claude has exactly the lines you cared about without you copying them.
The extension lives in the VS Code Marketplace, which is the built-in app store where extensions are listed. Search for "Claude Code" and install the one published by Anthropic.
1. Open VS Code Extensions panel (Cmd+Shift+X or Ctrl+Shift+X)
2. Search "Claude Code"
3. Install the extension by Anthropic
4. Open the Claude panel from the activity bar on the left
5. Sign in when promptedAfter install, open any project folder. The Claude panel shows the chat. The active editor file is already in context. A good first prompt to try: open a file, highlight a function you want to understand, and type "explain what this does in plain English." Claude responds based on exactly those lines.
You can also reference other files by typing @ followed by the filename. For example: @utils.js what does the formatDate function return? and Claude reads that file without you opening it or copying code.
Cmd+Esc (macOS) / Ctrl+Esc (Linux/Windows) → open Claude with current selectionThat keystroke is worth memorizing. Highlight code, hit the shortcut, ask the question.
The plugin works in IntelliJ IDEA, PyCharm, WebStorm, GoLand, RubyMine, and the rest of the JetBrains lineup. It is currently labeled as Beta.
1. Settings → Plugins → Marketplace
2. Search "Claude Code"
3. Install the Beta plugin by Anthropic
4. Restart the IDE
5. Open the Claude tool window from the side panelThe chat panel docks like any other JetBrains tool window. The diff viewer is the native JetBrains diff, so the experience matches what you already use for code review and merge conflicts.
Info
Warning: The JetBrains plugin is in beta. Expect rough edges. If a feature you need only exists in the VS Code version, that gap may not close immediately. Check the changelog before committing to JetBrains for serious work.
The terminal CLI, VS Code extension, and JetBrains plugin all read the same configuration files:
~/.claude/CLAUDE.md # global memory, all projects
~/.claude/settings.json # global permissions and preferences
<repo>/.claude/CLAUDE.md # project memory
<repo>/.claude/settings.json # project permissionsThis means your permissions, skills, hooks, and CLAUDE.md context work the same in every surface. Think of it like a phone's settings: you configure your notifications once and every app respects them. You do not reconfigure Claude each time you switch from terminal to IDE. Set them up once, use them everywhere. Switching surfaces does not lose your custom rules.
CLAUDE.md configuration is covered in detail in the next tutorials. For now, just know the file exists and the IDE version reads it the same way the terminal version does.
The IDE version is better for most everyday coding. The terminal is better for:
claude -p "do X" from another script. This is how Claude shows up in scheduled jobs and in automated test pipelines.Plenty of professional developers use both. IDE for project work, terminal for scripts and quick fixes. The configurations are shared, so the switch is cheap.
Info
Tip: You can run the CLI inside the IDE's integrated terminal. You get the IDE's editor for code review and the terminal's interface for chat. Some users prefer this hybrid mode over the dedicated chat panel.
If you are starting fresh and not sure which to pick, here is what I would do:
That gets you the best of both without forcing a choice you cannot reverse.
Claude Code runs as a CLI, a VS Code extension, and a JetBrains plugin. The IDE versions add context sharing, native diffs, checkpoints (VS Code), and conversation tabs. They all share the same configuration files, so switching surfaces is free. Start with the CLI, add the IDE extension that matches your editor, and keep the terminal around for scripts and remote work.
Next up: 04. Commands and Shortcuts.
Discussion
0 comments· Help other readers by sharing what worked (or didn't) for you.
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts!