Module 10 · Lesson 03
IDE Integration — VS Code and JetBrains
Reading time: 12 minutes Track: Claude Fluency for Teams · Developer path
Why IDE integration matters
Running Claude in a terminal tab alongside your editor works, but IDE integration removes the context-switching friction and puts Claude's capabilities directly in your workflow:
- See Claude's responses alongside your code
- Select code and send it directly to Claude without copy-pasting
- Apply Claude's suggested edits inline with a single click
- Maintain awareness of what files are open and what you're working on
VS Code
Installation:
- Open VS Code
- Open the Extensions panel (⌘+Shift+X / Ctrl+Shift+X)
- Search "Claude Code"
- Install the official Anthropic extension
- Sign in with your Anthropic account or API key when prompted
Key interactions in VS Code:
- Open Claude panel: Click the Claude icon in the Activity Bar (left sidebar)
- Send selected code: Select code → right-click → "Ask Claude about selection"
- Inline suggestions: Claude can suggest edits directly in your editor, shown as diff overlays you accept or reject
- Terminal integration: The Claude Code CLI and VS Code extension share session state — start a session in the terminal, continue it in the panel
Settings worth configuring:
{
"claude.autoApproveEdits": false,
"claude.showDiffBeforeEdit": true,
"claude.defaultModel": "claude-sonnet-4-6"
}
Always keep showDiffBeforeEdit: true in development environments.
JetBrains (IntelliJ, PyCharm, WebStorm, etc.)
Installation:
- Open your JetBrains IDE
- Go to Settings → Plugins → Marketplace
- Search "Claude Code"
- Install and restart
Key interactions in JetBrains:
- Claude tool window: View → Tool Windows → Claude
- Intention actions: With cursor on code, press Alt+Enter to see Claude-powered suggestions
- Code selection: Select code → right-click → Claude → "Explain" / "Refactor" / "Generate tests"
- Diff view: JetBrains' built-in diff viewer is used for showing Claude's proposed changes
Working with both CLI and IDE simultaneously
The CLI and IDE extensions are different interfaces to the same underlying Claude Code sessions. You can:
- Start a session in the CLI, continue in the IDE panel
- Use
claude --continuein the CLI to pick up where your IDE session left off - Switch between them mid-task without losing context
A common pattern: use the IDE extension for quick, inline questions and small edits; switch to the CLI for longer agentic tasks where you want to see full output.
Troubleshooting common issues
Authentication not persisting: Make sure ANTHROPIC_API_KEY is set in your shell profile (not just the current terminal session). IDE extensions spawn their own processes and may not inherit a one-time export.
Extension not seeing files: Claude Code needs to be opened from your project root. If the extension can't see your files, check that VS Code's workspace is set to the project directory.
Slow responses: Claude Code routes through the Anthropic API. Check your internet connection and API status at status.anthropic.com.