Claude Code Desktop App: a Tour for Non-Programmers
The Claude Code desktop app brings parallel sessions, visual diffs and live app preview to macOS and Windows — no terminal needed. Install guide and tour.
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.
What 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.
How do you install it and start the first session?
Download the installer from the official docs or claude.com/download — there's a universal macOS build and Windows x64/ARM64 installers. One honest limitation up front: there is no Linux desktop app; Linux folks use the CLI. On Windows, the Code tab also needs Git for Windows installed (restart the app after installing it).
Does it work on Mac and Windows?
Yes on both, no on Linux. macOS gets a single universal build that runs on Apple Silicon and Intel; Windows has separate x64 and ARM64 installers. The only platform-specific catch is the Windows one above — Git for Windows must be installed for the Code tab to work, and the app needs a restart after you add it.
First session in four moves
- 1Install, launch Claude, sign in with your Anthropic account, and click the Code tab at the top center. If it asks you to upgrade, you need a paid plan first.
- 2Choose where Claude runs: Local for your machine (pick this first), Remote for cloud sessions that survive closing the app, or SSH for a server you manage. Click Select folder and choose a small project you know well.
- 3Pick a model from the dropdown next to the send button, leave the permission mode on Ask permissions, and type a task: 'Find a TODO comment and fix it' is a classic opener.
- 4Review what Claude proposes: a diff view shows exactly what will change in each file, with Accept and Reject buttons. Nothing touches your files until you accept — and if you reject, Claude asks how you'd like to proceed instead.
Is 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.
What can it do that the terminal 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.
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.
Press Cmd+N (Ctrl+N on Windows) for a new session and give it a different task. Each session works in its own Git worktree — an isolated copy of your project — so two Claudes never overwrite each other's files. This is the feature that quietly doubles your output.
Cmd+/ show all keyboard shortcuts Cmd+N new session Cmd+W close session Ctrl+Tab next session Esc stop Claude Cmd+Shift+D toggle diff pane Ctrl+` toggle terminal Cmd+; open side chat Ctrl+O cycle view modes
Coming 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
Run this inside a CLI session: Claude saves the conversation, opens it in the desktop app, and exits the terminal. Available on macOS and Windows when signed in with a Claude subscription.
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.
Author
Evgeny Arsentyev
PhD · Chief Product Officer at a healthtech company
▌ Reading is the blue pill
Want to actually build this?
Guides explain. The free course transforms — personalized, gamified, and built to get you shipping fast.
◉ Take the red pill →