Lesson 466 of 2116
Claude Code IDE Integration: VS Code And JetBrains
Claude Code integrates into VS Code and JetBrains, making the terminal agent a first-class panel in the editor. The integration helps — but the CLI mental model still matters.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What the integration adds
- 2IDE integration
- 3panel UX
- 4diff viewer
Concept cluster
Terms to connect while reading
Section 1
What the integration adds
Claude Code in the IDE puts the agent in a side panel alongside your editor. You get richer diff viewing, click-to-open-file from the trace, and tighter integration with the editor's file selection (it can pick up which files you currently have open as initial context). The CLI is still in there — the IDE is a friendlier shell around it.
Where the IDE wins
- 1Side-by-side diffs that respect the editor's syntax highlighting and language server
- 2Right-click 'ask Claude about this' for surgical questions
- 3Selection-aware prompts (highlight code, ask about it, the model gets the selection as context)
- 4Quick toggle between agent panel and source
- 5Better integration with the editor's terminal for the agent's commands
Where the CLI still wins
- SSH into a remote server — the IDE integration may not follow you
- Long-running sessions you don't want bound to a window staying open
- CI and headless usage — IDE features don't apply
- When you want to script around the agent in shell pipelines
- Worktrees and parallel sessions — easier to manage from the terminal
Apply: pick your driver per task
Compare the options
| Task | Best driver |
|---|---|
| Quick refactor of a function | IDE panel — selection-aware |
| Cross-repo investigation | Terminal — easier to switch worktrees |
| Pair-programming a feature | Either, but pick one and stick |
| Headless review in CI | Terminal only |
| Demoing to a teammate | IDE panel — visual diffs |
Key terms in this lesson
The big idea: the IDE integration is a friendlier shell on the same CLI agent. Use it for visual workflows, keep the terminal for everything headless.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Claude Code IDE Integration: VS Code And JetBrains”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 9 min
What Perplexity Is: Search-Augmented LLM, Not A Chatbot
Perplexity is built around the idea that every answer should cite its sources. Treating it like ChatGPT misses the point — and the reliability gap that comes with it.
Creators · 10 min
Spaces: Building Team Knowledge Bases In Perplexity
Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They turn the search engine into a research workspace.
Creators · 10 min
Comet Browser: What It Does That Atlas And Operator Don't
Comet is Perplexity's full browser with a research-native sidebar and an action-capable agent. It plays differently than ChatGPT Atlas or Operator — and the differences matter.