Claude Code desktop vs CLI vs VS Code extension
Claude Code's desktop app, CLI, and VS Code extension run the same engine. What differs: features, scripting, parallel sessions, and when to use which.
A team rolls out Claude Code. Half the engineers live in the terminal, a few use the VS Code panel, and the designer who joined the pilot opens the desktop app. Then someone asks why /permissions doesn't work for them, and why the headless script from the wiki fails in the app. They're all running Claude Code, through three different front ends.
This guide compares the CLI, the desktop app, and the VS Code extension from Anthropic's desktop and VS Code documentation, checked on 16 November 2026.
The short answer
| CLI | Desktop app | VS Code extension | |
|---|---|---|---|
| Where it runs | Any terminal | Code tab of the Claude app | Panel inside VS Code |
| Commands | All | Most; terminal dialogs like /permissions aren't available | A subset |
| Permission modes | All, including dontAsk | Manual, Accept edits, Plan, Auto, and Bypass once enabled | Selectable in the panel |
Scripting (-p, Agent SDK) | Yes | No | No |
| Agent teams | Yes | No | Not in the extension docs |
| Parallel sessions | Separate terminals | Sidebar, each optionally in its own worktree | Tabs or windows |
| Reviewing changes | /diff, git | Visual diff view with comments | Inline diffs in the editor |
| App preview | No | Browser pane | No |
| Computer use | macOS, via /mcp | macOS and Windows | Not in the extension docs |
| Best for | Automation, power users, any editor | Parallel work and visual review | Staying in your editor |
What they share
The desktop app runs the same engine as the CLI, and the VS Code panel bundles its own copy of the CLI. All of them read:
CLAUDE.mdandCLAUDE.local.md- MCP servers in
~/.claude.jsonand.mcp.json - Hooks and skills
- Permission rules and other settings in
settings.json
So a team's setup carries over whichever front end each person picks. That's the most useful fact here: you configure the repository once. See Claude Code settings.json.
The CLI
The CLI is the complete version. Every command, every permission mode, claude -p for scripts and CI, the Agent SDK, and agent teams are CLI features. It works in any terminal, alongside any editor, and over SSH.
Use it if you live in the terminal, want to automate anything, or use an editor other than VS Code or JetBrains. See Claude Code headless mode for scripting.
The desktop app
Claude Code is the Code tab in the Claude desktop app, on macOS, Windows, and Linux (beta). What it adds:
- Parallel sessions in a sidebar, each optionally in its own git worktree
- Visual diff review with comments, and pull request status through CI
- A browser pane to preview your running app while Claude checks its own changes
- Panes for chat, diff, browser, terminal, and file editor side by side
- Computer use on macOS and Windows, to drive apps that have no CLI
- Scheduled tasks, and sessions started from your phone with Dispatch
- Cloud and SSH sessions from the same window
What it lacks: scripting (--print and --output-format), agent teams, the dontAsk mode, inline code completions, and terminal-dialog commands such as /permissions, which reply that they aren't available. Edit settings files for those instead.
Use it to run several tasks at once and review them visually, or for teammates who don't want a terminal.
The VS Code extension
The extension puts a Claude panel inside VS Code. It's built around the editor: inline diffs, @-mentions of files with line ranges from your selection, plan review before accepting, and several conversations in tabs.
Compared with the CLI, it supports a subset of commands, and has no ! Bash shortcut or tab completion. Installing the extension doesn't put claude on your PATH; for the CLI in VS Code's terminal, install it separately. A CLI running in the integrated terminal connects to the extension for diff viewing, and /ide connects one from an external terminal.
JetBrains IDEs get a plugin instead, which runs Claude Code in the IDE terminal and adds diff viewing and selection sharing.
Use it if you want to stay in your editor and review changes where you read code.
Moving between them
- CLI to desktop: run
/desktopin the session, orclaude --desktop --resume <session-id>. The app continues the same session, not a copy. - Desktop picking up a CLI session: type
/resumein the desktop prompt box. - Extension to CLI: the two share conversation history;
claude --resumein a terminal finds extension conversations.
More in how to resume a Claude Code session.
Which one to pick
- Solo developer, terminal habits: CLI, with the VS Code extension if you want inline diffs.
- Running several tasks at once: desktop app.
- CI, scripts, scheduled jobs: CLI only.
- PMs or designers trying Claude Code: desktop app, since it needs no terminal.
- A team: let people choose, and keep the shared setup in the repository so every front end gets it.
Where Lockstep fits
Because every front end reads the same configuration, a team only needs to set up shared context once. Lockstep's session briefings work through Claude Code hooks, which the CLI, desktop app, and extension all share, so each session starts with the team's approved decisions that apply to the work, captured from PRDs, Slack, and pull requests. Any MCP client can call Lockstep's tools directly.
See how it works.
Sources checked 16 November 2026
- https://code.claude.com/docs/en/desktop
- https://code.claude.com/docs/en/vs-code
- https://code.claude.com/docs/en/jetbrains
Related reading
For rolling Claude Code out across a team, see how to roll out Claude Code to an engineering team. For comparing Claude Code with other agents, see Claude Code vs Cursor vs Codex. For sessions that run in the cloud, see Claude Code cloud sessions. For Claude Code versus Cowork, see Claude Code vs Cowork. For the difference from the Claude app itself, see Claude Code vs Claude. For controlling a session from your phone, see Claude Code Remote Control.
Frequently asked questions
- Is Claude Code desktop the same as the CLI?
- It runs the same underlying engine with a graphical interface, in the Code tab of the Claude desktop app. Both read the same CLAUDE.md files, MCP servers, hooks, skills, and settings. The CLI has features the desktop app lacks, such as scripting with -p, the dontAsk mode, and agent teams.
- Should I use the Claude Code VS Code extension or the terminal?
- Use the extension if you want Claude beside your editor with inline diffs, @-mentions from your selection, and plan review in a panel. Use the CLI in VS Code's terminal when you need every command, the ! Bash shortcut, or tab completion. Both share conversation history.
- Does the VS Code extension include the CLI?
- It bundles a private copy for its chat panel, but it doesn't put claude on your PATH. To run claude in a terminal, install the standalone CLI separately.
- Can I move a session between the CLI and the desktop app?
- Yes. Run /desktop in the CLI to save the session and open it in the desktop app, or type /resume in the desktop app to pick up a session you started in the terminal on that computer. The desktop app continues the same session rather than a copy.
- Does Claude Code work in JetBrains IDEs?
- Yes, through a plugin for IntelliJ IDEA, PyCharm, WebStorm, GoLand, Android Studio, and other JetBrains IDEs. It runs Claude Code in the IDE's terminal and adds diff viewing and selection sharing.
Keep reading