The Claude web app on a Mac: giving it a window that stays put

Searching for the Claude web app usually happens at the point where a browser tab has stopped being good enough. The conversation is open somewhere in a strip of twenty tabs, the draft being worked on is in another, and switching between the two means reading favicons. Then a question arrives in chat, the tab gets closed by accident, and the thread has to be found again in the sidebar.

There are three different things that get called the Claude web app, and they behave differently on a Mac. One is the site running in an ordinary browser tab. One is the native application that Anthropic ships for macOS. One is the site installed as a standalone app by the browser itself, which looks native but is not. Picking between them is less about features than about which of them keeps a window where it was put, and which one survives having two accounts.

The native Mac app exists, and it is a download away

The first thing worth knowing is that this is not a case where a desktop application is missing. The download page lists a macOS build alongside Windows, a separate Windows arm64 build, ChromeOS and Linux. Mobile builds for iOS and Android are listed under a heading that describes them as pairing with the desktop app rather than replacing it.

That matters because it changes what the question is. Installing the native app is the shortest route to a Dock icon, a Cmd+Tab entry and notifications that carry the application's own identity rather than the browser's. The desktop section of that page describes it as all of Claude in one app, working with files and apps on the machine.

There is a second, separate download on the same page worth not confusing with it. A research focused application is listed in beta with its own builds, split into Mac (Apple Silicon) and Mac (Intel) as well as Windows and Linux. It is a different product from the main desktop app, so a search that lands on the split Apple Silicon and Intel downloads has landed on the research one.

The native app is the right default for a single account. The reason anyone ends up looking further is almost always the same, and it is covered below.

What the browser tab is actually costing

Before changing anything, it is worth naming the properties that are missing, because different routes restore different ones.

A tab has no fixed position. It moves every time something is opened or closed to its left, so it cannot be reached by muscle memory and has to be found by reading. A tab has no entry in the application switcher, so getting to it means getting to the browser first and then hunting. A tab is closable by the same reflex that closes everything else. And a tab's notifications arrive labelled as the browser, so a badge says that something wants attention without saying what.

One more cost is easy to miss. A tab loses its scroll position and its state whenever the browser is restarted, unless the session happens to be restored, so a long conversation reopens at the top. The routes below all fix that by giving the page a window the operating system knows about, which is why the fix feels larger than the setup time suggests.

Route	Dock icon	Cmd+Tab entry	Survives a browser restart	Two accounts at once
Ordinary browser tab	No	No	Only if the session is restored	One per browser profile
Native macOS app	Yes	Yes	Yes	Signed in as one account
Page installed as an app	Yes	Yes	Yes	One per installed copy
A browser that gives each app its own window	Yes	Yes	Yes	Yes, one window each

The first three columns are solved by any of the middle rows. The last column is the one that separates them, and it is the column most people do not check until after they have installed something.

Installing the page as an app, and the catch

Chromium based browsers can turn a page into a standalone bundle without any extra software. Google's documentation calls the result a web app and describes it as a website that works as an app, reachable from the launcher or the home screen. The path is the More menu, then Cast, save, and share, then Install page as app. On some sites an install control appears at the right of the address bar instead.

What arrives is a window with no tab strip, its own Dock icon and its own switcher entry. Two further things documented on the same page are useful afterwards. Installed web apps can be managed at chrome://apps, where right clicking one offers Create shortcut, so the app can be placed on the desktop or in a menu. The same right click menu offers Open at login, which starts the app automatically when the Mac is signed into. For anyone who wants a chat window present from the start of the day without adding it to a startup list, that is the control to use.

Removal is documented too: open the app, then More, then Uninstall, with an option to also delete the app's data from the browser. That last checkbox is worth reading before clicking, because deleting the data signs the account out and clears anything the site had stored locally, which is not usually what someone wants when they are only tidying the Dock.

Two documented details set installed web apps apart from a plain shortcut. Some of them get extra capabilities: more storage for offline content, notifications, file system access and icon badges. And Google's documentation notes that although web apps work offline, some may not work completely without an internet connection, so an installed chat window is still a network dependent thing. There is also a handling path for when an installed app tries to change its own name or icon. The browser notifies the user, and the update can be accepted, ignored, or the app uninstalled, which is the documented response when a name or icon change looks suspicious.

Now the catch. The installed app runs inside the browser profile that installed it, and nothing on the icon shows which profile that is. Installing the same page from two profiles produces two bundles with identical icons and identical names, distinguished only by position in the Dock. Renaming them immediately after installing is the difference between a working setup and a daily guess. This is the single most common way an installed web app goes wrong.

The account question is the one that decides it

For a personal machine with one account, the native app wins on simplicity and the discussion ends. The situation that sends people looking for alternatives is having more than one identity in the same service: a personal account and a work account, or a client's workspace alongside an employer's.

A native desktop app is signed in as one account at a time. A browser holds one signed in identity per profile, so two accounts means two profiles, and an installed web app inherits whichever profile installed it. Every one of those routes handles the second account by making the first one go away, which is the behavior that turns a five second switch into a thirty second one.

This is worth stating because it reframes the original search. Someone looking for the Claude web app on a Mac usually wants a window that stays put. Someone with two accounts also wants both of them reachable at once, and that second requirement is not satisfied by any route that stores one session per application.

There is also a browser extension route. The plan comparison on the pricing page lists Claude in Chrome as available on Pro and the Max tiers and not on the free tier, so an extension based workflow is a paid feature rather than a way around the window problem. It sits alongside the app rather than replacing it.

What the plan tier changes, and what it does not

Nothing about windows depends on the plan, but it is worth knowing where the lines fall before deciding that a limit is a technical one.

The free tier is listed at $0 and includes chat on web, desktop and mobile, web search, file creation, code execution, memory across conversations, connecting apps and tools, and artifacts. So the desktop app itself is not gated behind a subscription.

Pro is listed at $17 per month with the annual discount, billed as $200 up front, or $20 if billed monthly. What it adds, per the same page, includes more usage, handing off and scheduling tasks, the design, slides and docs surfaces, the coding tool, projects, more models, and the Chrome and Microsoft 365 integrations. Max starts at $100 per month and offers a choice of five times or twenty times the Pro usage, with higher output limits and priority access at busy times.

The practical reading is that hitting a usage ceiling is a plan question, while hitting a window or account ceiling is not. Upgrading does not make one desktop app hold two accounts.

Where one window per app fits

The third approach stops treating this as a single case to be solved and changes the container for every web service in daily use. Each service gets a window, an icon and a switcher slot, and each window carries its own signed in session. A chat assistant is then one window among six or seven, which is the point: two windows can hold two accounts of the same service without either being signed out, and closing one has no effect on the rest.

That is a larger change than installing one application, and it earns its place only for someone whose day genuinely lives in several web services rather than one. The organising unit is described under Workspaces, the behavior that follows from it is listed under Features, and whether the specific services in a given routine are covered is the question that actually decides it, which is answered by the list of supported apps. For anyone who also keeps a terminal open next to those windows, the built-in terminal covers that case.

The trade-offs are real and worth naming. Another browser is another piece of software to keep updated and another store of session cookies. Extensions do not always follow. Windows that stay resident use more memory than tabs that get closed during the day. None of that disqualifies the approach, but it is the reason to decide rather than to install and hope. Comparable tools have existed for years, and the differences between them are set out under Compared with Wavebox, with the cost side under Pricing.

What to change first

For one account, install the native macOS app from the download page and stop there; it solves the Dock icon, the switcher entry and the notification identity in one step. For two accounts, install it for the account used most and put the second one in something that keeps its own session, rather than signing in and out of the same window. If the day already contains five or six web services with this pattern repeating across all of them, the container is the thing to change, which is what SpaceDeck is built around.