Update, October 31, 2026: Desktop now runs on Linux too (Ubuntu and Debian, in beta), and a local session without a worktree no longer needs Git, Windows included. Git is still what gives each session its own worktree.
The terminal will always win for technical work: you're closer to the code, closer to the layer you want to affect. But not everyone wants to get their hands dirty with the terminal. Product Managers, Project Managers, technically capable people who don't live in code — for them, Desktop is the perfect entry point. Same engine as the CLI, with five exclusive capabilities on top.
Result:
┌─────────────────────────────────────────────┐
│ Chat │ Cowork │ ● Code │
├─────────────────────────────────────────────┤
│ Sessions │ Diff: app.tsx +12 -1 │
│ ▸ feature-auth│ - const old = getValue() │
│ ▸ fix-navbar │ + const r = compute(input) │
│ + New session │ [Accept] [Reject] [Review] │
└─────────────────────────────────────────────┘
The 5 exclusive features
1. Visual diff review with inline comments
Claude edits files and a +12 -1 indicator appears. Click to open the diff view. Click any line to leave a comment. Claude reads your feedback and adjusts the code. Cmd+Enter (macOS) or Ctrl+Enter (Windows and Linux) sends all comments at once.
2. Parallel sessions with automatic worktrees
+ New session creates an isolated worktree with no flags, no extra terminals. Each session gets its own branch, visible in the sidebar. The CLI requires claude -w <name> per terminal — Desktop abstracts it entirely. What it leaves behind is yours too: every session keeps its worktree on disk until you archive it.
3. Embedded app preview
A built-in browser shows your running app. Claude starts the dev server, takes screenshots, inspects the DOM, fills out forms, and fixes issues it finds. Configuration lives in .claude/launch.json:
That same pane now browses external sites too, not just your localhost. What it is exactly, and how it differs from the Chrome extension, is here.
{
"configurations": [{
"name": "web",
"runtimeExecutable": "npm",
"runtimeArgs": ["run", "dev"],
"port": 3000
}]
}
4. PR monitoring with auto-fix and auto-merge
After opening a PR, a CI status bar appears in the session. Auto-fix: Claude reads failures and patches them. Auto-merge: Claude merges when all checks pass. Requires gh CLI installed. When Auto-fix acts, the session gets the "Received a CI event" message.
5. Built-in connectors
+ button → Connectors to hook up GitHub, Slack, Linear, Notion, and more — no JSON editing. These are MCP servers with a graphical setup flow. In the CLI, configuring an MCP server means editing ~/.claude.json by hand.
Reference
| Feature | CLI | Desktop |
|---|---|---|
| Diff review | Not available | Visual with inline comments |
| Parallel sessions | claude -w manual |
Automatic from sidebar |
| App preview | --chrome (beta) |
Embedded browser |
| CI monitoring | Not available | Status bar + auto-fix |
| Connectors | Edit JSON manually | Graphical UI |
| Concept | Detail |
|---|---|
| Engine | Same as the CLI — shares CLAUDE.md, hooks, MCP |
| Platforms | macOS, Windows and Linux (Ubuntu and Debian, in beta) |
| Environments | Local, Remote (Anthropic cloud), SSH |
| Models | Opus, Sonnet, Haiku — locked at session start |
Those environments are now saved with a name and a shortcut, with Remote Control added: Claude Code Desktop environments.
Related: Claude Code in VS Code: the native panel · The 6 ways to extend Claude Code · Worktrees for parallel tasks · Computer use — when the terminal is not enough · /tasks panel for parallel work
Official docs: Get started with Desktop · Full reference
Requirements
- Pro, Max, Teams, or Enterprise subscription
- macOS, Windows or Linux (Ubuntu 22.04 or later, Debian 12 or later; in beta)
- Git installed for worktree sessions (on Windows: git-scm.com); a session without a worktree starts without it