Skip to content
Back to articles
claude-codedesktop-appguiworkflowanthropic

Claude Code Desktop: a GUI for people who hate the terminal

The native Mac and Windows app swaps the terminal for windows and clicks: parallel sessions, visual diff, embedded preview, permission modes. Same engine as the CLI.

9 min read

Claude Code Desktop: a GUI for people who hate the terminal

A native app for Mac and Windows replaces the terminal with windows and clicks, keeps the same engine as the CLI, and adds a few things the command line could never deliver well.

The black prompt scared a lot of people away

You open a Claude Code tutorial. The first screenshot is a black screen with a blinking $. If you grew up clicking icons and dragging windows, that looks like an involuntary trip back to the 80s. You close the tab before installing anything.

That barrier has always been there. Developers get along with the terminal, but most of the people who want to build an app with AI, including designers, product managers, business folks and completely non-technical users, don't have that habit. On April 14, 2026, Anthropic rebuilt the Claude Code GUI from the ground up, shipping parallel sessions, a drag-and-drop workspace, and an experience designed for working outside the terminal.

What Claude Code Desktop actually is

It's a tab called Code inside the Claude Desktop app. The app has three tabs:

Tab Purpose
Chat General conversation with no file access, like claude.ai
Cowork Autonomous agent running in a cloud VM in the background
Code Interactive assistant with direct access to your local files

The Code tab is Claude Code with a graphical interface. Same engine as the CLI, same configuration (CLAUDE.md, MCP, skills, hooks), but now with a sidebar, docked panels, visual diff, embedded browser, and Accept/Reject buttons for every change.

Supported platforms:

  • macOS (universal build for Intel and Apple Silicon)
  • Windows x64
  • Windows ARM64 (separate installer)
  • Linux: not supported

Plan required: Pro, Max, Team, or Enterprise. The free plan opens Chat but keeps the Code tab locked.

The download is a regular .dmg or .exe installer. No Node.js, no npm, no WSL, no environment variables. Download, install, sign in with your Anthropic account, click Code.

Not just a CLI skin

The obvious move would have been to turn every CLI command into a button. Anthropic went further. The Code tab ships features the terminal simply can't deliver well.

Parallel sessions with automatic Git worktrees

Click + New session in the sidebar. Each session gets an isolated copy of the project via Git worktree, zero configuration. One session refactoring auth, another fixing a payment bug, a third writing tests, all on the same project, no conflict, no git stash, no stepping on each other. When the PR merges, the session archives itself if you enable Auto-archive after PR merge or close.

The CLI caught up (v2.1.49 added native worktree support), but you still have to set it up and juggle multiple terminals. On Desktop it's the default: one click, one worktree.

Visual diff with inline comments

After Claude edits files, an indicator like +12 -1 appears. Click to open a side-by-side diff with the file list on the left. Click any line to open a comment box. Write feedback, press Cmd+Enter (or Ctrl+Enter on Windows), and send all comments at once. Claude reads them and revises. Same dynamic as a GitHub pull request review, but inside the app.

Embedded preview

The app starts your dev server and mounts the browser in a side pane. Click an HTML file in chat, it opens in preview. Ask for a layout tweak and you watch it update live. With autoVerify on (the default), after every edit Claude takes screenshots, inspects the DOM, clicks elements, and confirms the change works before handing control back.

For a custom dev command, edit .claude/launch.json:

{
  "version": "0.0.1",
  "configurations": [
    {
      "name": "my-app",
      "runtimeExecutable": "npm",
      "runtimeArgs": ["run", "dev"],
      "port": 3000
    }
  ]
}

PR monitoring with auto-fix and auto-merge

Once a pull request is open (you or Claude opens it), a CI status bar appears in the session. Two toggles:

  • Auto-fix: Claude reads the failure log and tries to fix CI on its own
  • Auto-merge: when every check passes, the PR gets squash-merged automatically

Requires the GitHub CLI (gh) installed and authenticated. If it's not there, the app prompts you to install it the first time.

Computer use (research preview)

Claude can open applications, click your screen, and drive the mouse. Useful for testing a native app in a mobile simulator, filling in desktop tools with no CLI, or automating anything that only works through a GUI. It ships off by default and has to be enabled in Settings → General. On macOS, you also have to grant Accessibility and Screen Recording permissions.

Available only on Pro and Max plans, on macOS and Windows. Not available on Team or Enterprise.

Side chat that doesn't pollute the main thread

Press Cmd+; (or Ctrl+; on Windows). A side chat opens that can read everything in the main thread up to that point, but whose response never gets added back to the main conversation. Use it to ask "why does this file exist?", check an assumption, or explore an idea without polluting the context of the task Claude is working on.

Permission modes: control without commands

The dropdown next to Send has five autonomy levels:

Mode Behavior
Ask permissions Asks before every edit or command. Default for new users.
Auto accept edits Auto-accepts file edits and filesystem commands like mkdir, touch, mv. Still asks for other commands.
Plan mode Explores and proposes a plan without editing anything. Great before a large refactor.
Auto Runs everything with background safety checks. Research preview. On Max, requires Opus 4.7; on Team, Enterprise, and API accepts Sonnet 4.6, Opus 4.6, or Opus 4.7. Not available on Pro or third-party providers.
Bypass permissions No prompts at all. Equivalent to --dangerously-skip-permissions in the CLI. Use only inside sandboxed containers or VMs.

Anthropic's own advice: start complex work in Plan mode, approve the plan, then switch to Auto accept or Ask.

Who it's for (and who it isn't)

It's for:

  • Anyone who never used a terminal and wants to start building with AI without learning cd and ls first
  • Developers who prefer reviewing diffs side-by-side over reading patches in a terminal
  • People running multiple tasks in parallel who don't want to manage worktrees by hand
  • Mac and Windows teams
  • Visual work: landing pages, dashboards, frontend apps, anywhere seeing the preview next to the code speeds things up

It's not for:

  • Linux users (no official support)
  • Free plan accounts (paid subscription required)
  • CI pipelines or automation (the CLI is still the right tool there)
  • Flows that depend on dontAsk (that mode only exists in the CLI)

Community reception

The redesign was announced on April 14, 2026 and drew immediate buzz on Twitter/X. The screenshot that circulated most showed two Claude Code sessions running side by side inside the same window, with a recurring take: Anthropic crossed a line the competition is still months away from, turning Claude Code from "AI pair programmer" into something closer to "AI operations platform."

The most common complaint wasn't about the app itself but about token consumption. The New Stack ran the headline "Anthropic's redesigned Claude Code desktop app lets you burn through tokens even faster," and users on Reddit and GitHub reported that sessions which used to last hours were burning limits in minutes. The combination of parallel sessions, auto-verify after every edit, and PR monitoring eats context fast. Desktop makes running several things at once so easy that it's easy to lose track.

On r/ClaudeAI the overall mood was positive about features (automatic worktrees got the loudest praise) and negative about cost. VentureBeat read the redesign as the first serious sign that Anthropic now treats the graphical app as a primary workspace, not a CLI side dish.

In Practice

Step-by-step to install and run your first local session:

1. Download the installer

Go to claude.com/download and pick your platform. On Windows, confirm whether you're on x64 or ARM64 and grab the right one.

2. Install Git (Windows only)

Without Git, the Code tab doesn't work for local sessions. Download from git-scm.com/downloads/win. On Mac, Git usually comes preinstalled. Verify with:

git --version

3. Open Claude, sign in, click Code

Use your Anthropic account. If clicking Code prompts you to upgrade, your plan doesn't unlock the tab yet. If it asks you to sign in online, complete the sign-in in your browser and restart the app.

4. Set up the session

In the prompt box, choose:

  • Environment: Local (to run on your machine)
  • Project folder: click "Select folder" and point to an existing repository
  • Model: pick from the dropdown next to Send
  • Permission mode: start with Ask permissions

5. Write the first task

Start small. Something like:

Read the README and create a CLAUDE.md summarizing the code conventions of the project

Press Enter. Claude proposes edits and shows each diff before applying. Accept or reject one at a time.

6. Open a second session in parallel

Click + New session in the sidebar or press Cmd+N (Mac) / Ctrl+N (Windows). Pick the same folder. This new session runs in an isolated worktree, no collision with the first. Switch between sessions with Ctrl+Tab.

Tip: Cmd+/ (or Ctrl+/ on Windows) shows every available shortcut. Worth a look before you start.

Limits you'll run into

  • No Linux: macOS and Windows only. Ubuntu, Fedora, and friends stay on CLI or Claude Code on the web.
  • Remote sessions have fewer features: Ask permissions doesn't exist there (remote sessions auto-accept file edits), and @mention for files doesn't work.
  • Terminal pane is local-only: on SSH or remote sessions, Ctrl+` won't bring up a terminal.
  • Computer use has prerequisites: Pro or Max plan, macOS or Windows, explicit activation, and on Mac, OS-level permissions.
  • New layout requires an updated build: the drag-and-drop workspace needs Claude Desktop v1.2581.0 or later. Use Claude → Check for Updates (Mac) or Help → Check for Updates (Windows).

The CLI didn't die, it got a neighbor

Desktop doesn't replace the terminal. It runs the same engine, reads the same CLAUDE.md, recognizes the same skills, uses the same MCP servers. You can run the terminal and Desktop at the same time on the same project. Inside the app, the Continue in button sends the current session to the web or to VS Code with one click.

The difference is who you are and what you're doing. Automation in CI, scripting inside a pipeline, piping tail into claude -p? CLI. Reviewing visual diffs, running three experiments in parallel, watching the app preview next to the code, trying things without leaving the window? Desktop.

Bottom line

A little over a week after the redesign, Claude Code Desktop delivered:

  • A real entry point for people who freeze at the terminal
  • Parallel sessions with automatic worktrees, no setup
  • Visual diff, embedded preview, integrated terminal, and PR monitoring in one app
  • Same engine as the CLI, so every CLAUDE.md, MCP server, and skill you already configured works with no tweaks
  • Computer use in research preview for anyone who needs to drive a native app
  • An open debate about how much token it burns, worth tracking before you make it the team default

If the terminal was the reason you kept putting off Claude Code, that reason is gone.

References