Appearance

Language

Mastering AI agents

Claude Code Desktop vs CLI vs VS Code (2026): Which One Should a Beginner Start With?

The Claude Code desktop app, the terminal CLI and the VS Code extension run the same engine and share CLAUDE.md and settings. If you've never used a terminal, start with the desktop app: install, sign in, open the Code tab and pick a folder. Use the extension if you already live in VS Code, and the CLI for scripting, automation and every command.

Kelvin Wang · · 9 min read

What they share: the project’s CLAUDE.md, ~/.claude/settings.json and MCP configuration, plus the same Claude account and the same usage allowance. The desktop app’s Code tab sits in the sidebar, and you don’t need to install Node.js or the CLI. All three need a paid Claude plan (Pro, Max, Ultra, Team or Enterprise); the free plan can’t use them. The terminal and VS Code can also run on a Console (API) account billed by usage, while the desktop app is subscription only. Routing the desktop app through a company LLM gateway or a provider such as Amazon Bedrock takes a separate third-party inference setup in the app 3. Based on Anthropic’s official docs as checked on November 7, 2026, with the desktop provider details rechecked on November 9.

The three side by side

ItemDesktop appTerminal (CLI)VS Code extension
How to installDownload an installer (macOS, Windows; Linux in beta)One install commandSearch "Claude Code" in the VS Code extension marketplace
Need to know the terminal?NoYesBarely
How you review changesVisual diff; you can comment on a specific lineText diff in the terminalSide-by-side diff in the editor
Commands and featuresMost; a few terminal-panel commands don't workAllA subset (type / to see which)
Automation (claude -p, scripts)NoYesNo (run the CLI in the built-in terminal)
Several tasks at onceMultiple sessions in the sidebarMultiple terminal windowsMultiple tabs or windows
Permission modesManual, Accept edits, Plan, Auto; Bypass can be turned onAll, including dontAskManual, Edit automatically, Plan, Auto

Sources: Desktop docs [3], VS Code docs [4], Overview [1].

Beyond these three there’s also the web version (claude.ai/code 9, which runs in the cloud with nothing installed on your machine) and a JetBrains plugin (IntelliJ, PyCharm, WebStorm and others, which needs the CLI installed separately).

Desktop app: no terminal required

Install and first run

  1. Download the installer from the Claude Code desktop quickstart 2. On macOS it’s a universal build for both Intel and Apple Silicon; Windows has x64 and ARM64 builds; Ubuntu and Debian install through apt (beta).
  2. Open Claude after installing and sign in with your Anthropic account.
  3. Click the Code tab at the top of the sidebar. If you see an upgrade prompt, your account doesn’t have a paid plan yet.
  4. In the row under the prompt box, set the first control to the first option under Local (runs on your own computer), then use the folder control next to it, choose Open folder…, and pick your project folder.
  5. Choose a model from the model picker on the right of the same row, then type in the prompt box, for example “Write a CLAUDE.md for this project.”

The desktop app ships with Claude Code built in, so the Code tab works without Node.js or the CLI 2.

Permission modes

The row under the prompt box sets how much Claude can do without asking you first:

  • Manual: asks before every file edit or command and shows a diff for you to accept or reject.
  • Accept edits: accepts file edits and file commands such as mkdir and mv automatically, and still asks about other terminal commands.
  • Plan: reads files and proposes a plan without changing any code. Use it before large changes to check the direction.
  • Auto: doesn’t ask about each step; a background classifier checks every action against what you asked for and blocks risky ones.

If you’re new, start in Manual and loosen it once you understand what each step does. After Claude edits files, a marker like +12 -1 appears near the prompt box. Click it to open the diff view, go through it file by file, and leave a comment on any line to ask for a change.

What the desktop app adds

  • Preview pane. Start a dev server in the app and the site opens in a built-in browser pane. Claude can see the page too, so it can look and edit in the same loop.
  • Sessions side by side. The sidebar holds several tasks at once, each with its own conversation and changes.
  • Scheduled tasks. Set up work that runs daily or weekly.
  • Attachments. Attach images and PDFs directly.
  • Cloud and SSH. Besides Local, the environment can be Cloud (keeps running after you close the app) or SSH (connects to a remote host); Windows also has WSL.

What the desktop app can’t do

  • No non-interactive mode like claude -p, so it can’t go into scripts or CI.
  • Agent teams (several Claudes splitting up work) are CLI only.
  • Commands that open an interactive panel in the terminal, such as /permissions, don’t work in the Code tab. Edit the settings files directly or run them from the CLI.
  • It connects to Anthropic’s API by default and doesn’t read environment variables such as ANTHROPIC_BASE_URL. For an LLM gateway, your company can push the configuration to you, or you can turn on Developer Mode under Help → Troubleshooting and enter the gateway URL in Developer → Configure Third-Party Inference. To run on Amazon Bedrock, Google Cloud’s Agent Platform or Microsoft Foundry, follow the official third-party deployment docs 10.

Git is optional in the desktop app: you only need it if you turn on worktrees (each session works in its own branch folder). You still need Git to push your site to GitHub, and for Claude to open pull requests and follow CI results from the desktop app you also need the GitHub CLI (gh).

Terminal (CLI): the most complete

The CLI is the original form of Claude Code, and the official docs call it the “full-featured CLI”: the VS Code extension supports only some commands, and the desktop app has no non-interactive mode and can’t run a few terminal-panel commands, while the CLI has all of it. Installing takes one line. On macOS, open the Terminal app; on Windows, open PowerShell (the prompt starts with PS C:\):

# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash
# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

The installer doesn’t show progress. When it finishes, open a new terminal window and run claude --version. If it prints a version number, you’re set. If it says claude can’t be found, the install location isn’t on your PATH yet; follow the official troubleshooting page 6. Then cd into your project folder and run claude. The first run signs you in through the browser. On Windows, installing Git for Windows is recommended, because Claude Code runs commands through its Git Bash; without it, Claude Code falls back to PowerShell and still works 5.

When the CLI fits:

  • Automation. claude -p "..." runs once and exits, so it can sit in a shell script, a scheduled job or CI. You can also pipe another command’s output into it, for example git diff main --name-only | claude -p "check these files for security issues".
  • Every command. Configuration commands like /hooks, /permissions and /plugin all work.
  • The finest-grained permissions. On top of the desktop modes there’s dontAsk, which allows only pre-approved tools.
  • Running on a server. On a machine with no graphical interface you need the CLI; the desktop app’s SSH mode is for driving a remote machine from your own computer.

The downside is that everything is typed: no mouse, arrow keys to move around, and diffs in plain text.

Go deeper Claude Code Tutorial 2026: Install, CLAUDE.md, Skills, and Your First Website The CLI from install to a live website, then skills, hooks and MCP.

VS Code extension: inside your editor

Install

You need VS Code 1.94.0 or later. Open Extensions (Cmd+Shift+X on macOS, Ctrl+Shift+X on Windows), search for “Claude Code” and click Install. Cursor and other VS Code forks are supported too.

Once installed, there are several ways to open it: the Spark icon at the top right of the editor when a file is open, the Spark icon in the Activity Bar on the left, the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) with “Claude Code”, or ✻ Claude Code in the status bar at the bottom right 4.

What works well

  • Inline diffs. In Manual mode, changes show side by side in the editor and are only written once you accept them.
  • Referencing a selection. Select some code and press Option+K (macOS) or Alt+K (Windows) to insert a reference like @file.ts#5-10.
  • Editable plans. In Plan mode the plan opens as a Markdown document; add comments in it and hand it back.
  • Shared history with the CLI. A conversation from the extension can be picked up in the terminal with claude --resume; settings, plugins and MCP configuration carry over as well.

Things to watch for

The extension supports only some commands (type / to see the list), and it has neither the CLI’s ! shortcut for running shell commands nor Tab completion. When you need those, open the CLI in VS Code’s built-in terminal.

You can mix all three

Configuration is shared, so you don’t have to pick just one 3:

  • The project’s CLAUDE.md and CLAUDE.local.md, MCP servers in ~/.claude.json and .mcp.json, hooks, skills and settings in ~/.claude/settings.json are read by both the desktop app and the CLI.
  • Running /desktop in the CLI saves the current conversation, opens it in the desktop app and exits the CLI. It needs a Claude subscription sign-in and works on macOS and x64 Windows.
  • Typing /resume in the desktop prompt box picks up a conversation started in the CLI; after that, claude --resume in the terminal still finds the same conversation.
  • The VS Code extension and the CLI share conversation history.

A common combination: review diffs and talk things through in the desktop app or VS Code day to day, and open a terminal in the same project when you need a script or a CLI-only command.

Which one to use first

Pick based on where you are now:

Your situationStart withWhy
Never used a terminal, just want to build somethingDesktop appInstall, pick a folder and review diffs with the mouse, no commands to type
Already use VS Code or CursorVS Code extensionYou stay in the editor and see changes right next to the file
Need automation, a server, or every featureTerminalOnly the CLI has claude -p and the full command set
Your computer runs LinuxTerminalThe desktop app is still in beta on Linux
No computer of your own at hand, or you want work to run in the cloudWebRuns at claude.ai/code with nothing to install

Whichever you start with, you can switch later: CLAUDE.md and the settings travel with the project.

I mostly use the terminal version myself.

Does it cost the same?

Yes. All three sign in with the same Claude account and draw on the same plan allowance; the terminal and VS Code on a Console account are billed at API rates instead. On November 7, 2026, the official pricing page listed the individual plans as Pro at US$20 a month, Max at US$100 and Ultra at US$200, before tax 8.

Sources

  1. 1. Overview · Claude Code Docs · checked 2026-11-07
  2. 2. Get started with the desktop app · Claude Code Docs · checked 2026-11-07
  3. 3. Use Claude Code Desktop · Claude Code Docs · checked 2026-11-07
  4. 4. Use Claude Code in VS Code · Claude Code Docs · checked 2026-11-07
  5. 5. Advanced setup · Claude Code Docs · checked 2026-11-07
  6. 6. Troubleshoot installation · Claude Code Docs · checked 2026-11-07
  7. 7. Terminal guide for new users · Claude Code Docs · checked 2026-11-07
  8. 8. Plans & Pricing · Anthropic · checked 2026-11-07
  9. 9. Claude Code on the web · Anthropic · checked 2026-11-07
  10. 10. Connect Claude Code to an LLM gateway · Claude Code Docs · checked 2026-11-09

About the author

Kelvin Wang

Electrical engineer building tools with AI agents, sharing hands-on notes on engineering and investing.

More about me