There are two Claudes that look nearly identical. One is claude.ai in a browser tab, the other is the Claude desktop app. They share your account, so it is easy to treat the app as the website in a window. The real difference is where it runs: on your machine, and that single fact opens a category of work the browser cannot reach.
Here is what the desktop app actually adds.
Four surfaces in one window
The app is a home for several modes that used to be separate things:
- Chat is the conversation you already know from the website, with desktop touches on top: a global shortcut to start a thought from anywhere, voice dictation, and on a Mac the ability to hand Claude a screenshot or a window.
- Cowork is the agent that does knowledge work on your computer, the folder wrangling, the report drafting, the data pulling. It is desktop only, and it is the subject of its own post.
- Code is the Claude Code development surface with a graphical view of diffs, a terminal, and git, the same engine as the command line tool covered in the tour of the non-terminal surfaces.
- Dispatch lets you start a task from your phone and have the desktop run it while you are away, then ping you when it is done.
The point of having them in one window is that they share the same account, memory, and projects, so moving from a quick question to a full task to a coding job does not mean moving between tools.
What the browser cannot do
Everything above could almost live in a tab. The next few genuinely cannot.
Local files are the big one. On the web, Claude works with what you upload. On the desktop, you point it at a folder on your machine and it reads the files there directly, and with your approval it can write them, so you stop pasting snippets back and forth and point Claude at the work itself.
From there the list grows. It can drive your real applications, clicking and typing through them when a task needs it, which is what powers Cowork and Dispatch. It can run jobs on a schedule too, though only while the app is open and the machine is awake; a job whose time passes while the app is closed or the computer is asleep just runs the next time you open it. On top of that come the native operating system touches the web cannot reach, a quick entry shortcut, dictation, grabbing a window, plus connectors for local tools, which deserve their own section.
Connectors: handing it your tools
Connectors are the app's most underused feature, its name for plugging in outside tools and data through the Model Context Protocol. There are two ways in.
Desktop Extensions are the easy route. Open Settings, go to Extensions, and install a connector in one click from the directory or from a packaged file. Claude Desktop ships with what these need to run, so there is usually nothing else to install, and any keys a connector asks for are stored in your operating system's secure keychain rather than a plain text file.
For anything not packaged as an extension, you edit the config file under Settings, Developer, Edit Config, and add the server yourself. One thing to know: the desktop app and the Claude Code command line tool keep their connector setups separate, so a server you want in both you add to each. The exception is a project's own .mcp.json file, which both can read when you check it into the repo. Keep the set small either way. A handful of connectors is fine; piling on twenty will slow the app's startup and eat memory. And connect only to servers you trust, since a connector that can act for you can also be hijacked by instructions hidden in the content it reads, which is the prompt injection risk.
Getting it, and what needs a paid plan
Download it from claude.com/download. There are builds for macOS, on a recent version, as a universal app that runs on both Intel and Apple Silicon, and for Windows 10 or newer on both x64 and ARM machines. There is no native Linux build; on Linux you use the Claude Code command line tool instead. One Windows gotcha: install Git before the first time you open the Code tab, then restart the app.
The app is free to download, and Chat works on the free plan. The parts that make the desktop app worth installing, Cowork and the Code tab, need a paid plan, Pro or above. The current breakdown of who gets what lives on the pricing page.
When the desktop app is the right call
Reach for the desktop app when you want Claude to touch your actual machine: your files, your local tools through connectors, your applications through computer use, or a job that should run on a schedule where you work. The browser is still the right answer for a quick question on a device that is not yours, or when you have no reason to give it local access at all. You never have to commit to one, so pick whichever fits the moment.
If you are wiring a lean one person operation together, the desktop app is where your local tools, agents, and code all meet. That is the same build it yourself spirit behind The $100 Network, which is about running a portfolio of small sites without a team, exactly the kind of setup where one well configured machine does the work of several.
Related reading
- Claude Cowork goes deep on the knowledge work agent that lives in this app, including the safety model for letting it operate your computer.
- Claude Code Without the Terminal maps the Code tab against the other ways to run Claude Code.
- Run /init First is the groundwork that makes the Code tab start informed instead of blind.
- The Task You Should Never Have Been Doing is the deciding question for any computer-use agent: which work should you actually hand off.
Fact-check notes and sources
- What the desktop app is, its surfaces, platforms, and install: Claude Desktop download, Install Claude Desktop, and the Claude Code desktop docs.
- Local MCP servers, Desktop Extensions, and connector setup: Getting started with local MCP servers on Claude Desktop.
- Dispatch and computer use: Dispatch and computer use.
- Plans and what each tier includes: Claude pricing.
Written from my own hands-on use of Claude's tools. Mentions of Claude, Claude Code, Claude Cowork, Dispatch, and Anthropic are nominative; this site is independent, and no affiliation or endorsement is implied.
