ChatGPT as a Mac app: what it does and where it breaks down

A tab does not have an icon you can aim at. That is the whole problem. ChatGPT sits in a browser window with fourteen other things, and finding it costs a scan of the tab strip every time. The phrase ChatGPT as a Mac app points at the fix, but it names three different jobs that behave differently once they are done. Knowing which one you are actually doing decides whether the result holds up or annoys you in a week.

Three things wear the same name

The first job is installing the desktop app that OpenAI publishes. It is a real application with its own process, its own update channel, and features that a web page cannot have.

The second job is asking a browser to carve a page out into its own window. Safari has Add to Dock. Chrome has Install page as app. Both produce an icon, and both leave the page running on the browser that made it.

The third job is building a standalone Mac app around a URL using a tool made for that purpose. The result is an application with its own session store, its own icon, and rules about where links are allowed to go.

All three put something in the Dock. All three join Command Tab. The difference is ownership: who owns the process, who owns the login session, and who owns the icon. Those three questions predict every problem that shows up later.

What the official app owns

The OpenAI desktop app owns the process, so it can do things a web page cannot. A keyboard shortcut opens a small bar anywhere on the desktop, set to Option Space by default and changeable in settings. From that bar you can attach a file, add a photo, or take a screenshot and hand it straight to the model. The bar is also reachable from a menu bar icon, and it can be dragged anywhere on screen.

It also owns the requirement list. The system requirements are macOS 14 and either Apple Silicon, meaning M1 or better, or an Intel processor. The help center is direct about the floor:

We will not be releasing a version of the app that is compatible with older operating systems. Source: help.openai.com

That single sentence closes the first road for anyone on macOS 13 or earlier, and it is the cleanest fork in the whole decision.

There is one more thing the official app owns right now, which is a name change. As of July 9th the new desktop app combines Chat, Work, and Codex, and the previous macOS app was renamed ChatGPT Classic. Classic is not discontinued. It continues to receive model updates, bug fixes, and security patches, and it keeps support for its existing enterprise capabilities. Some newer agent features land only in the new app. The new app can install next to the old one, which is why two similar icons sometimes appear in the same Dock.

What the new app changed inside the window

The July change was not only a rename. The new app puts three modes under one roof and gives them a navigation model. ChatGPT or Codex is selected from a menu at the top left. Inside ChatGPT, a toggle at the top of the page switches between Chat and Work. Chat threads and Work threads then appear together in Recents, where they can be sorted, filtered, and pinned, and existing Projects carry over. From inside a project, starting a Chat and starting a Work thread are two separate choices, with the Work thread picking up the project context.

Codex keeps its own view and its own history, separate from the rest. Its workflows did not change in the move. Cloud Work threads sync across web, mobile, and desktop, so a Work thread started on a phone shows up on the Mac and can be continued there. Codex threads do not work that way: Codex cannot be selected on the web or on mobile, although supported desktop Codex threads can be reached from the Remote tab in the mobile app.

This matters for the Dock question because it changes what one icon now represents. Before the change, the icon meant a chat window. Now it can mean a chat window, a document workspace, or a coding session, depending on which view was left open. Anyone who keeps all three in play gets more out of a single dedicated icon than out of a tab, because the app remembers where it was.

What the official app does not do

It signs in once. One account, one window, one session. If a work account and a personal account both need to stay logged in, the desktop app is not the place where that gets solved.

It also keeps its own icon. There is no supported way to make the work copy look different from the personal copy, because there is only one copy. None of this is a fault. It is a shape, and the shape decides whether one app is enough.

The shortcut is the other constraint people hit. Option Space is popular real estate. Third party launchers claim it, and so do window managers and clipboard tools. Two pieces of software cannot both answer the same chord, and macOS gives no warning that a conflict exists. The symptom is a shortcut that suddenly opens the wrong thing, or nothing at all. The fix is not complicated, since the shortcut is editable in settings, but it has to be done deliberately rather than discovered by accident a month later.

One more shape worth naming: the app is tied to an update channel you do not control. That is usually an advantage, since fixes arrive without effort. It becomes a consideration when a layout changes under you, as it did in July, and muscle memory built over months has to be rebuilt in an afternoon.

What a browser built app owns

Safari's Add to Dock is the shortest route that exists. The confirmation sheet says plainly that an icon will be added to your Dock and Launchpad so you can quickly access this website. Note both destinations. Removing the icon from the Dock later does not remove it from Launchpad, which is why these things seem to come back from the dead.

Chrome takes a different path to the same result. The install command sits under the menu, in Cast, save, and share, as Install page as app, and some sites also show an install control at the right of the address bar. Chrome documents one behaviour worth knowing about: when a web app wants to change its own name or icon, Chrome interrupts and lets you accept, ignore, or uninstall it. If the icon in your Dock quietly becomes something else, that prompt is where it came from.

What the browser keeps is the session. A page installed from a browser profile shares that profile's cookies and logins. Sign out in the browser and the installed window signs out too. For a single account this is invisible. For two accounts it means the profile has to be split first, and every installed icon belongs to whichever profile created it.

What a wrapper tool owns

A tool built for turning sites into Mac apps owns the container, so it can separate what the browser route cannot. Each app gets its own session, which is the reason two accounts can sit side by side in the Dock without any switching. Each app gets its own icon, chosen at build time. Each app can carry rules about where a link opens: inside the app, in a different app, or out to a browser.

The trade is a floor of its own and a few decisions up front. Coherence X6 requires macOS 13.5 or later and builds on Chromium engines, which is what makes browser extensions available inside the resulting app. Unite Pro requires macOS 15 or later and builds on WebKit, with window modes that include a menu bar app and a sidebar app. Both let you build a first app at no cost. Which one fits depends less on price than on whether an extension has to come along for the ride. The Features page is a faster way to compare those behaviours than reading marketing copy, because the settings are listed one by one.

Where each one breaks down

Failure has a pattern, and the pattern is different for each road.

Road	Breaks down when	Usual symptom
Official app	The Mac runs macOS 13 or older	Installer refuses, no version is coming
Official app	A launcher already uses Option Space	Shortcut opens the wrong thing
Browser install	Two accounts need to stay signed in	Every open requires a switch
Browser install	The icon is removed from the Dock only	It survives in Launchpad
Wrapper app	Link rules were never set	Clicks scatter between app and browser
Wrapper app	Notification permission was skipped	The app stays silent and looks broken

The table is worth reading as a checklist before building anything, because five of those six rows are decisions made at setup time. Only the first is a hardware and operating system fact that no amount of care can route around. Everything else is a choice that costs a minute now and an hour later.

One failure is shared by all three. Entry points multiply. The desktop app, a pinned tab, and a built app all point at the same service, and after a week nobody remembers which one holds the half finished conversation. Deleting the losers is part of the job, not an afterthought.

Picking the road by counting, not by preference

Two numbers settle this faster than any feature list. How many times a day does the service get opened, and how many accounts sign into it.

Open it once or twice a day with one account, and a browser install is enough. Nothing else earns its setup time. Open it constantly with one account, and the official app wins, because the Option Space bar removes the act of finding a window at all. Use two or more accounts, and a wrapper tool is the only road that keeps both logged in at once, regardless of how often either is opened.

These roads also combine. Screenshot handoff exists only in the official app. Parallel sessions exist only in separate containers. People who need both run both and give them different jobs. The Supported services list is useful at this stage for a reason that has nothing to do with ChatGPT: it shows which of the other sites in your tab strip are worth the same treatment, and those are usually where the bigger time savings sit.

What to change first

Pick one number to act on: the count of accounts. One account, install the official app if the Mac is on macOS 14 or later, and stop there. Two accounts, build separate containers with Kagemusha and give them icons you can tell apart at a glance.