IDE Integration
Claude Code Inside Your Editor
Video Lesson Coming Soon
A video walkthrough for this module is in production. For now, dive into the written content below.
What You'll Learn
- ✓ VS Code extension setup
- ✓ JetBrains plugin features
- ✓ The inline editing flow
- ✓ Sharing context with your editor
- ✓ Terminal vs IDE: when to use which
In this module 6 sections
VS Code Extension
The VS Code extension brings Claude Code directly into your editor. Instead of switching between your terminal and your editor, you get a sidebar panel for conversations, inline diffs showing proposed changes, and the ability to select code and ask Claude Code about it.
The extension uses the same Claude Code engine as the terminal — same AI model, same capabilities, same CLAUDE.md configuration. The only difference is the interface.
Setting Up VS Code
Open VS Code, go to Extensions (Ctrl/Cmd+Shift+X), and search for "Claude Code". Install the official Anthropic extension.
The extension uses the same authentication as the terminal CLI. If you have already logged in via the terminal, you are ready. If not, the extension will prompt you to log in.
Click the Claude Code icon in the sidebar or use the Command Palette (Ctrl/Cmd+Shift+P) and search for "Claude Code: Open in New Tab".
The panel works like the terminal interface. Type a prompt, and Claude Code responds with full awareness of your open project.
JetBrains Plugin
If you use IntelliJ IDEA, WebStorm, PyCharm, or any other JetBrains IDE, the Claude Code plugin gives you the same core experience.
Install it from the JetBrains Marketplace by searching for "Claude Code". It adds a tool window for conversations and opens proposed edits in the IDE's standard diff viewer — the same diff interface you already use for git changes.
The Inline Editing Flow
How Inline Diffs Work
- Claude Code proposes a change to a file in your project
- The IDE shows the change as an inline diff — green for additions, red for deletions
- You can review each change individually, accept or reject specific parts
- Accepted changes are applied directly to your file
- Rejected changes are discarded without touching your code
- Multiple changes across multiple files are shown as a batch you can review all at once
Sharing Context with Your Editor
Your IDE extension sees your open files, your cursor position, and your selected text. Use this to your advantage. Select a function, then ask "add error handling here." Select a test, then ask "why is this failing?" The more precise your selection, the more precise Claude Code's response.
Terminal vs IDE: When to Use Which
| Task | Best Surface | Why |
|---|---|---|
| Multi-file refactoring | Terminal | Broader codebase context, faster file scanning |
| Quick fix in one file | IDE | Inline diffs show changes exactly where they go |
| Code exploration | Terminal | Faster for reading many files in sequence |
| Writing tests | IDE | See implementation alongside the test you are writing |
| Git operations | Terminal | Full control over commits, branches, and PRs |
| Code review | IDE | Visual diffs in the context of surrounding code |
| Debugging errors | Terminal | Better for tracing across multiple files |
| Learning new code | Either | Both work well — pick your preference |
Key Takeaways
VS Code and JetBrains extensions use the same Claude Code engine as the terminal with an editor-native interface
Inline diffs show proposed changes as green/red highlights you can accept or reject individually
Terminal is better for broad codebase operations; IDE is better for focused, file-level edits
Selecting code before prompting gives Claude Code precise context and produces more accurate results