The window looks like one product. Open it and you see three tabs at the top: Chat, Cowork and Code. Underneath, the reality is messier. Age of Product has published a breakdown arguing that those three tabs are really three separate programs sharing a single shell. The behavior most users stumble on makes sense once you accept that framing: instructions written in one tab do not travel to another, uploaded help files vanish when you switch, and any preference you set can quietly reset.
This piece walks through what the split means for people who treat Claude Desktop as one tool, what the install actually supports, and how a team should approach setup without losing a day to it.
At a glance:
- The top of Claude Desktop shows three tabs: Chat, Cowork and Code.
- Each tab operates inside its own sandbox with its own memory and its own way of handling instructions.
- Cowork and Code are built on a shared agent foundation; Chat lives on a separate stack.
- Anything you configure in one tab, like custom instructions, uploaded files or tool preferences, stays in that tab.
- Claude Desktop runs on macOS, Windows and Linux (beta), with Linux install paths through an apt repo or a direct .deb.
Why three tabs feel like one app
The tab bar is the only surface most people ever look at. From the outside, Chat, Cowork and Code look like three views into the same product. They are not. Age of Product describes each tab as a distinct application with its own context, its own persistence rules and its own memory of what you told it last time.
The familiar surprise goes like this: you spend twenty minutes in Chat, upload a help file, write careful instructions, set your preferences, then pop over to Cowork and find a clean slate. That is not a glitch. It is what the architecture produces, because nothing about the two tabs shares state.
What is actually different under the hood
The split matters for three reasons, and the table below maps the tabs to what is going on behind them.
| Tab | Where it runs | Memory and sandbox | What that means for you |
|---|---|---|---|
| Chat | Anthropic's cloud servers | Separate stack, no local file access | Good for ad-hoc questions, bad for cross-tab reuse |
| Cowork | A Linux virtual machine on your machine, wiped between sessions | Sandboxed folder access, no carryover from Chat | Great for delegated work, frustrating for setup |
| Code | Your native terminal, no sandbox | Full system access, aimed at engineers | Powerful, but the wrong place to do light drafting |
Each of those rows is its own product. That is the mental model to keep, even when the window only shows one tab bar.
Installation and platform support
Claude Desktop is offered for macOS, Windows and Linux, with Linux still labeled beta. The two Linux flavors that are explicitly listed as supported are Ubuntu 22.04 LTS or newer and Debian 12 (bookworm) or newer, on either x64 or arm64 hardware.
The official guidance, as described in Anthropic's support documentation, points Ubuntu and Debian users toward an apt repository rather than a one-off download. Installing from that repo lets normal system update routines pull new versions in. Before you trust the source, the help docs publish a key fingerprint that you can verify, and they explicitly warn that downloading the .deb will not opt you into those regular updates.
The global hotkey for Quick Entry is documented as working on X11, and on Wayland it falls back to whatever GlobalShortcuts portal your desktop session provides. On Windows and macOS, the install is a standard download followed by launching the app from the Applications folder or Start menu and signing in.
Who should care about this split
Three groups should pay attention. People setting up Claude for personal use, so they do not waste an afternoon configuring a tab they never use. Team leads rolling the app out, because a shared setup doc is useless if the configuration does not cross tabs. And anyone comparing Claude Desktop to competitors, because the trade-off here is real safety and isolation in exchange for less continuity.
If you are an Agile practitioner, the analogy is familiar: it is the same reason a Definition of Done lives on the team wiki, not in a single developer's head. The instructions have to be put in the right place for them to actually do their job.
Worked example: setting up Claude for a content team
Say you are rolling Claude Desktop out to a small content team. They want Cowork for repetitive drafting and Chat for one-off questions. The trap is treating the setup as a single project.
Run it as two. In Cowork, build the skills, the folder layout and the CLAUDE.md files that encode your house style. In Chat, set up the lighter instructions that shape tone for short conversations. Treat the two tabs as separate products with separate config files. The first time someone asks why their Chat answers ignore the style guide, the answer is obvious: Chat was never told to use it.
What to watch next
Three things are worth tracking. Whether Anthropic eventually bridges the three tabs with shared memory, or keeps the walls high for safety reasons. Whether Linux support moves out of beta and how the apt repo path holds up across new Ubuntu and Debian releases. And whether the desktop extensions directory becomes a real ecosystem or stays a curiosity.
Until then, treat Claude Desktop as three products behind one icon. Configure each tab for the job it actually does, and stop expecting setup to follow you around.
Key takeaways
- Chat, Cowork and Code are three apps with one tab bar, and configuration does not cross between them.
- Cowork and Code share an underlying agent foundation; Chat is a separate system with its own memory.
- On Linux, install through the apt repo for regular updates, and verify the published signing key fingerprint first.
Frequently asked questions
Are Chat, Cowork and Code the same app?
No. Age of Product's breakdown describes each tab as a separate application with its own sandbox and memory.
Why does my Claude setup vanish when I switch tabs?
Anything you configure, such as custom instructions, help files and tool preferences, is scoped to the tab you set it up in.
Do Cowork and Code share an architecture?
Yes. Anthropic's documentation frames Cowork as built on the same agent foundation as Claude Code, with Chat sitting on a different stack.
Which platforms support Claude Desktop?
MacOS, Windows and Linux (beta). On Linux, supported distributions include Ubuntu 22.04 LTS or later and Debian 12 or later, on x64 or arm64.
What is the recommended Linux install path?
Anthropic's support docs point Ubuntu and Debian users at the apt repository so updates arrive with the system, and they publish a key fingerprint to verify first.