Claude Code vs VS Code
Claude Code vs VS Code puts an agent next to an editor. Visual Studio Code is the cross-platform editor you write in. Claude Code is Anthropic's agent that reads a project, edits files, and runs commands, including from a panel inside that editor. If you want the official docs as lessons with quizzes, paste the URL into the AI course builder.
What VS Code is
Visual Studio Code is a code editor for Windows, macOS, and Linux. The docs describe one workbench: open a file or a whole project and stay in the same window for editing, running, debugging, testing, and source control.
The editor gives you:
- IntelliSense completions, parameter info, and inline documentation for supported languages
- Navigation to definitions, references, and symbols
- An integrated terminal that runs a full shell in the workspace
- Built-in Git for staging, commits, branches, worktrees, and merge conflicts
- A debugger with breakpoints, and a Testing view that uses testing extensions
- Extensions for languages and tools that are not already built in
JavaScript, TypeScript, CSS, and HTML ship in the box. Other languages come from the Marketplace. The download page calls VS Code free and built on open source. The product site also calls it an open source AI code editor and a home for multi-agent development. You can hand work to agents that plan, change code, and run commands, using Copilot or a third-party provider such as Claude or OpenAI.
VS Code is the place the files stay open. It can host agents. Claude Code is one agent you can run there.
What Claude Code is
Anthropic's overview calls Claude Code an agentic coding tool. It reads your codebase, edits files, runs commands, and connects to your development tools. The same engine runs in the terminal, in IDE extensions, in a desktop app, and in the browser.
In the terminal you install it, change into a project, and run claude. The first session asks you to log in. Most surfaces need a Claude subscription or an Anthropic Console account. The terminal CLI, VS Code, and JetBrains also support third-party providers.
A session gathers context, takes action, and checks the result. Search tools find files and match text. Execution tools run the shell, tests, and git. File tools read and edit. A question about the project can stay in the gathering step. A bug fix cycles through all three.
How they fit together
Anthropic's platform page lists VS Code as the surface for working inside the editor. What you get is inline diffs, the integrated terminal, and file context. The CLI is listed on its own, for terminal workflows, scripting, and remote servers, and the docs call it the most complete surface. IDE extensions trade some CLI-only features for visual review and a tighter fit with the editor.
The VS Code extension is the recommended way to use Claude Code in the editor. It needs VS Code 1.94.0 or later, and a paid Claude plan (Pro, Max, Team, or Enterprise) or a Claude Console account. After you install it from the Extensions view, you open the panel, sign in, and type a prompt. Claude can see the file you have open and any text you select. You can @-mention a file or a folder. Plan mode writes a plan as Markdown and waits. Manual mode shows a side-by-side diff and asks before an edit.
The extension bundles its own copy of the CLI for that panel. The claude command in a terminal comes from the standalone install. The extension does not add claude to your PATH. Run that install once, then open the integrated terminal and run claude. The CLI can share diffs and diagnostics with the IDE. The extension and the CLI share conversation history, so claude --resume continues a panel session from the terminal.
Anthropic's own table compares those two Claude Code surfaces:
| Feature | CLI | VS Code extension |
|---|---|---|
| Commands and skills | All | A subset; type / to see what is available |
| MCP server config | Yes | Yes, with /mcp in the chat panel |
| Checkpoints | Yes | Yes |
! Bash shortcut | Yes | No |
| Tab completion | Yes | No |
Checkpoints rewind file edits from the conversation. Remote actions such as a database write stay outside that rewind.
Which one you open
Open VS Code when you are writing, jumping to a definition, debugging, or reviewing a diff yourself. Open Claude Code when you want the agent to search the project, edit more than the current file, or run a command and read the output.
Use them together. Keep VS Code as the editor. Use the Claude Code panel when you want inline diffs and plan review. Use the CLI in the integrated terminal when you need a command the panel leaves out, such as the ! Bash shortcut or tab completion.
If the goal is to study a public repository, paste the URL on GitHub to course. Ailurn turns that repo into a structured course in the same workspace, with quizzes and flashcards from the material. Free includes planning and one lesson from a prompt. File attachments start on a paid plan. Ailurn does not issue accredited certificates.
A short setup
- Install VS Code and open the project folder.
- Install the Claude Code extension, or install the CLI and run
claudein the integrated terminal. - Sign in with the same Claude account you use elsewhere. On Pro or Max, IDE usage counts toward the same limits as Claude and Claude Code in the terminal.
- Ask what the project does before you ask for an edit. Plan mode reads the files and waits for approval.
VS Code is where the code stays open. Claude Code is the agent that can work on it from inside that window or from the shell.