Claude Code inside the editor: the VS Code and JetBrains add-ons
Where the developers you work with actually run Claude Code
After this, you'll be able to describe the VS Code and JetBrains add-ons as two more doors into the same Claude Code engine, recognize what you are seeing when a developer uses one, and explain why a non-developer does not need to install them.
Before you start
Complete The Code tab in the desktop app first; this lesson builds on that by showing two more surfaces for the same tool, this time living inside a developer's code editor.
The idea
Two Claude Code surfaces live inside a code editor: an add-on for VS Code and one for JetBrains. A code editor is the program developers write software in, and an add-on is an extra piece you install into it. These do not create a new Claude Code; they put the same tool right next to the code a developer is already working on.
Like every Claude Code surface, they require Claude Code access through your plan. This is where most developers actually use Claude Code day to day, because their code already lives in the editor. For you, the value is recognizing the scene, not installing one.
Here is the before and after: Before, you watch a developer work, see Claude responding inside a busy editor full of code, and assume it is yet another product you have never heard of. After, you recognize it instantly: that is Claude Code, reached through the VS Code or JetBrains door. Same engine, different room.
Now try it: name the two editor doors out loud, VS Code and JetBrains, and say the sentence that ties them to the module. These are the same Claude Code engine living inside the editor a developer already uses.
Same engine, now living inside the editor, where you recognize it rather than install it.
Try it (9 min)
Watch out for
- Thinking the editor add-ons are a different product. They are the same Claude Code engine, reached through the VS Code or JetBrains door.
- Trying to install one to 'keep up.' These live inside a developer's editor; a non-developer recognizes them rather than runs them.
- Expecting them to work on a free plan. Like every Claude Code surface, the editor add-ons need a plan with Claude Code access.
- Assuming you must read the code on screen. When you see a developer using one, you can still ask Claude what a change does in plain English.
- Confusing the editor itself with the add-on. VS Code and JetBrains are the editors; the add-on is the extra piece that brings Claude Code inside them.
Paste this into Claude
I am not a developer, but the people I work with use code editors all day. I want to understand the Claude Code editor add-ons well enough to recognize them. Please: 1. Explain, in plain English, what a "code editor" is and what an "add-on" (or extension) does to one. 2. Tell me what the VS Code and JetBrains add-ons for Claude Code actually do, and confirm they are the same Claude Code engine as the desktop and terminal versions, just inside the editor. 3. Confirm whether they require Claude Code access through your plan. 4. Tell me honestly whether I, as a non-developer, would ever install one, or whether I just need to recognize it when a developer is using it. Explain every technical term the moment you use it. Assume I have never written code.
What good looks like
- Claude defines 'code editor' and 'add-on' in plain English
- Claude confirms the VS Code and JetBrains add-ons are the same Claude Code engine, living inside the editor
- Claude confirms they require a plan with Claude Code access
- Claude tells you a non-developer recognizes them rather than installs them, and never asks you to write code
When this breaks
- Breaks when you count the editor add-ons as separate tools because they share the one Claude Code engine, so what you learned about the desktop and terminal surfaces still applies.
- Breaks when a non-developer tries to install one because the add-ons assume you already work inside VS Code or JetBrains, which is a developer's setup, not yours.
AI can help with this
Open Claude and paste this: 'Explain the VS Code and JetBrains add-ons for Claude Code in plain English. Confirm they are the same tool as the desktop version, just inside an editor, and tell me whether a non-developer needs to install one.'
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that claude defines 'code editor' and 'add-on' in plain English.
- You can verify that claude confirms the VS Code and JetBrains add-ons are the same Claude Code engine, living inside the editor.
- You can verify that claude confirms they require a plan with Claude Code access.
- You can verify that claude tells you a non-developer recognizes them rather than installs them, and never asks you to write code.
Key takeaways
The VS Code and JetBrains add-ons are two more doors into the same Claude Code engine, this time inside the editor a developer already uses. They are plan-gated like every surface, and a non-developer recognizes them rather than installs them.
- Treat the VS Code and JetBrains add-ons as two more doors into one Claude Code engine, not new products.
- Recognize the scene when a developer runs Claude Code inside their editor instead of asking what unfamiliar tool it is.
- Remember the add-ons are paid, like every Claude Code surface.
- Leave installing them to developers; your job is to recognize the surface and read its output.