Claude Code Desktop App: a Tour for Non-Programmers

The Claude Code desktop app is Claude Code with buttons instead of a black terminal window: you pick a project folder, type what you want in plain language, and review every proposed change as a visual diff with Accept and Reject buttons. It runs on macOS and Windows, includes everything it needs (no Node.js, no CLI install), and is the gentlest way I know to start building with AI.

I recommend it to every non-programmer who emails me 'where do I even begin?'. The terminal version is powerful, but the desktop app lets you see what's happening — and seeing is what builds trust in the first week.

1What is the Claude Code desktop app, exactly?

The Claude desktop app has three tabs: Chat for regular conversations (like claude.ai), Cowork for autonomous background work in a cloud VM, and Code — the one we care about — for software development with direct access to your local files. In the Code tab, each conversation is a session with its own chat history, project folder, and changes. The sidebar lists your sessions, and yes, you can run several in parallel: for Git repositories each session gets its own isolated copy of the project via Git worktrees, so experiments never trample each other.

2How to install Claude Code on your desktop and start the first session

Download the installer from the official docs or claude.com/download — there's a universal macOS build, Windows x64/ARM64 installers, and a beta .deb for Ubuntu 22.04+ / Debian 12+. Linux support is new and still in beta. On Windows, you only need Git for Windows if you turn on isolated worktrees for parallel sessions — a plain local session doesn't require it anymore.

Does it work on Mac and Windows?

Yes on all three. macOS gets a single universal build (Apple Silicon and Intel); Windows has separate x64 and ARM64 installers; Linux (Ubuntu 22.04+, Debian 12+) has a beta .deb package installed via apt. The only platform-specific catch: on Windows, Git for Windows is only required if you use isolated worktrees for parallel sessions, not for the Code tab in general; on Linux, Computer Use and voice dictation are not yet available in the desktop beta — use the CLI for those.

3Is the desktop app free to use?

The download is free, but the Code tab requires a Pro, Max, Team, or Enterprise subscription — same requirement as Claude Code everywhere else. There's no separate 'desktop' fee, and cloud sessions you start from the app count against your normal plan limits with no extra compute charge. If clicking Code prompts you to upgrade, that's the subscription check talking.

4Claude Code desktop app vs the terminal: what can it do that the CLI can't?

Quite a lot, and this is where it gets fun. Panes: arrange chat, diff, live preview, integrated terminal, and a file editor side by side, drag-and-drop. PR monitoring: after you open a pull request, a CI status bar appears with Auto-fix and Auto-merge toggles. Side chats: press Cmd+; (Ctrl+; on Windows) to ask a question that reads the session's context without derailing it. And Dispatch: message a task from your phone, and it can spawn a Code session on your computer while you're out.

Two additions I now use constantly: `/diff` opens a live side panel instead of a modal — it lists every changed file with line counts, refreshes as you edit, and lets you select specific lines to attach to your next prompt. And any pane — diff, terminal, whatever — can be popped out into its own window, dragged to a second screen, then docked back when you're done.

Can Claude preview and test my app?

Yes — this is the Preview feature, and it's the one terminal users miss most. Claude starts your dev server in an embedded browser and verifies its own changes: it takes screenshots, clicks around, and fixes what it finds. Instead of you switching to a browser to check whether a button works, Claude checks for you and reports back, all inside the app.

On macOS, there's now a background computer-use mode (beta, Pro and Max plans): Claude can see and act in apps you've approved while you keep working on something else — so it's not blocking your screen while it runs a long task.

5Coming from the CLI — or heading there?

Desktop and CLI run the same engine and share configuration: CLAUDE.md memory files, MCP servers, hooks, skills, and settings all work in both. You can run both at once, even on the same project. And there's a one-command bridge:

/desktop

/resume

Practical kicker: install the app tonight, point it at the messiest folder of half-finished ideas you have, and ask Claude to 'create a CLAUDE.md with instructions for this codebase'. You'll watch it explore your project in the diff view — and you'll have onboarded yourself and the AI in one move.