Day 8 of 52 · about 15 min · Basics
Use Claude Code in VS Code or JetBrains
If you live in your editor, review Claude’s changes there. A side-by-side diff is easier to read, and to reject, than a patch scrolling past in a terminal.
You’ll finish with
- Claude Code running in your editor, signed in
- An edit you accepted or rejected in the editor’s diff view
You’ll need
- A Claude Pro, Max, Team or Enterprise plan, or a Console account
- VS Code 1.94.0 or later, a fork such as Cursor, or a JetBrains IDE
- JetBrains only: Claude Code installed in your terminal (Day 1)
Before you start
Tell us about your setup and the steps change to fit it. Your answers stay in this browser, and you can change them at any time.
Which system are you on?
Commands differ between systems. Pick the one you’ll run Claude Code on.
Which editor do you use?
The steps
One step at a time. When a step’s check matches, tick it and the next one opens.
Step 1 of 3: Install the integration
Add the Claude Code extension or plugin.VS Code and forks
- Open Extensions:
Cmd+Shift+Xon Mac,Ctrl+Shift+Xelsewhere - Search “Claude Code”, select Install
JetBrains IDEs
- Install the Claude Code plugin from the JetBrains Marketplace
- Restart the IDE
The VS Code extension is self-contained. The JetBrains plugin runs your installed CLI. Check it worked
VS Code: a Spark icon in the Activity Bar. JetBrains: a Claude Code button after the restart.
If it didn’t work
The VS Code extension doesn’t appear
Restart VS Code, or run Developer: Reload Window from the Command Palette.
- Open Extensions:
Step 2 of 3: Open Claude Code from the editor
Start a session linked to your editor.In order:
You
Open your project
You
Start Claude Code
Spark icon in VS Code;
Cmd+EscorCtrl+Escin JetBrainsYou
Sign in the first time
If you started it in another terminal
Run /ide to connect
Started from the editor, it connects by itself. For “A JetBrains IDE”
The plugin runs
claudein the IDE terminal. Open the project at its root so Claude sees its files.Check it worked
You can type a prompt. After
/ide, Claude Code confirms with a message likeConnected to IntelliJ IDEA.If it didn’t work
`/ide` says “No available IDEs detected”
Check the plugin is enabled and restart the IDE. On WSL2, see the JetBrains WSL notes.
Step 3 of 3: Review an edit in the diff view
Switch to Manual mode, ask for an edit, decide in the diff.Auto mode edits most files without asking, so switch to Manual. VS Code: click the mode indicator under the prompt box, pick Manual. JetBrains: press
Shift+Tabuntil the status bar shows⏸ manual mode on.Then paste thisAdd one sentence at the end of README.md that says how to run the tests.In order:
You
Ask for an edit
Claude
Claude proposes it
Tool
Editor shows a side-by-side diff
If you accept
The edit is saved
If you reject
The file stays unchanged
If you edit the diff first
Claude is told you changed it
In Manual mode, every edit waits for you. Check it worked
The diff opens side by side in your editor. Accept it and the sentence lands in
README.md.If it didn’t work
In JetBrains, the diff shows in the terminal
Run
/configand set Diff tool toauto.
Finish · 3 of 3 steps to go
Your editor is the review screen
What you’ll have checked
- Claude Code opens in your editor, signed in
- You accepted or rejected an edit in the editor’s diff
Lesson updates by email
Get lesson updates by email
Leave your email and we’ll tell you when we add or update a lesson.
Claude Code for your team
Want Claude Code set up across your team?
HorizonLux sets up and repairs Claude Code for teams: CLAUDE.md rules, hooks that enforce them and reviewed MCP servers. Book a free call to talk it through.
Related
Questions
Questions about Day 8
Can I use the terminal version inside VS Code?
Yes, with the standalone CLI installed: run `claude` in the integrated terminal and it uses VS Code for diffs.
Sources
Checked against the official Claude Code docs on .
Independent resource, not affiliated with Anthropic. HorizonLux wrote this lesson; Claude Code is made by Anthropic.