Copilot Mac app: which one exists, and which one does not

Searching for a Copilot Mac app returns three different products with the same first word, and only one of them has an icon to download. That is the whole reason the search is confusing. Somebody who wants the assistant that answers questions, somebody who wants the version tied to a work email address, and somebody who wants code completion in an editor are all typing the same thing and needing three different answers. Sorting out which one is being looked for takes about a minute and saves an afternoon.

Three products, one word

What it is called Where it runs on a Mac Who it is for

Microsoft Copilot A downloadable app in the Mac App Store, plus copilot.microsoft.com Personal accounts, general assistant

Microsoft 365 Copilot A web address inside a Microsoft 365 tenant Work and school accounts, tied to company data

GitHub Copilot Inside an editor, as an extension Writing code

The first is the consumer assistant. It has a Mac App Store listing under Microsoft Corporation, and the listing describes the app as being for macOS specifically rather than an iPad app running on Apple silicon.

The second is a different product that happens to share the brand. It is reached through a Microsoft 365 sign in and shows results drawn from the files, mail, and chats inside an organisation. There is no separate Mac App Store listing carrying that name. Searching the Mac App Store for it returns the consumer Copilot app and the Office apps, and nothing else.

The third is not a standalone application at all. It lives inside Visual Studio Code, Visual Studio, the JetBrains editors, and a handful of others, and it is installed the way any editor extension is installed. There is no icon for it in Applications, and there never was.

Most of the frustration in this search comes from wanting the second or third thing and being handed the first.

What the Mac App Store listing actually says

The consumer app is worth reading before installing, because a few lines in the listing decide whether it is usable at all.

Requires macOS 14.0 or later. Source: apps.apple.com

That cutoff rules out a Mac still on Ventura or older, which is a meaningful share of machines that are otherwise perfectly capable. On those, the browser is the only route, and no amount of searching for a download will change it.

The rest of the listing: developer Microsoft Corporation, category Productivity, age rating 13+, download size around 128.9 MB, and interface languages listed as English plus 32 more. The price is free, with in app purchases. On the United States storefront those in app purchases are Microsoft 365 subscriptions rather than a Copilot specific tier, which means the app itself is the front door to a subscription that also covers the Office applications.

The Mac version arrived later than the mobile ones. Apple's listing dates the first Mac release to February 2025, well after the iPhone and Android versions were established. That gap matters when reading older articles: guides written in 2024 that say no Mac app exists were correct when published.

When the account is a work account

This is where most installations go wrong. The consumer app is built around a personal Microsoft account. An organisation that has bought Copilot for its Microsoft 365 tenant is buying something else, and that something else is delivered as a web surface at a Microsoft 365 address rather than as a separate download.

There are practical consequences.

The first is that a company laptop with the App Store app installed can end up with two Copilots open, one signed into a personal account and one in a browser tab signed into work. They do not share history, and they do not see the same data. Which one is in front decides what the answer is based on.

The second is that the work surface is subject to conditional access policies, device compliance checks, and whatever sign in requirements the tenant has configured. A browser handles all of that correctly because it is the environment those policies were designed around.

The third is the one people actually feel: the work surface has no icon. It is a URL, so it is a tab, and a tab that gets closed by accident sits behind however many other tabs are open. That is the gap a standalone window fills, and it is a different problem from the one the App Store solves.

GitHub Copilot has no separate app to install

Worth stating plainly because the search term does not distinguish it. GitHub Copilot is an extension. Installing it means opening the extensions panel in an editor, installing it there, and signing in with a GitHub account. A search of the Mac App Store for it returns unrelated third party utilities, none of them published by GitHub.

There is a related surface at github.com that answers questions in the browser, and that one is a website like any other. If the goal is a window on the desktop that opens straight to it, the route is the same as for any other site with no native client.

Confusing the two costs real time. Someone looking for code completion who installs the consumer assistant gets a chat window that has never seen the repository and cannot autocomplete anything in an editor.

The billing is separate too, which is the fastest way to tell them apart when a listing is ambiguous. The coding product is billed through a GitHub account. The consumer assistant on the Mac App Store carries Microsoft 365 subscriptions as in app purchases. The tenant product is billed per seat by an organisation. Three different invoices means three different products, regardless of what the icons look like.

One more signal helps when reading search results. Articles that describe a Copilot Mac app with a Dock icon, voice input, and image generation are describing the consumer assistant. Articles that describe it summarising an email thread or pulling a figure out of a company file are describing the tenant product. Articles that show it finishing a function are describing the editor extension. The screenshots give it away faster than the headlines do.

The Office apps are a fourth place the name appears

There is one more source of confusion, and it catches people who already installed the standalone app and wondered why nothing changed inside their documents.

Word, Excel, PowerPoint, and Outlook for Mac are separate Mac App Store listings, each published by Microsoft Corporation and each currently requiring macOS 14.0 or later. Assistance that appears inside those applications is part of those applications. Installing the standalone Copilot app does not add anything to a spreadsheet, and removing the standalone app does not take anything away from one. They are unrelated installs that happen to share a brand.

This is worth checking before troubleshooting. Someone whose actual goal is help writing inside a document has no reason to install a separate chat application, and someone who wants a chat window has no reason to reinstall Office. The question to ask is where the work happens: inside a file, or inside a conversation.

The same logic applies to the browser. Edge ships a sidebar with the assistant built in, which is not the Mac App Store app either, and behaves like part of the browser rather than part of the system. A Mac user who tried it there and then went looking for a matching download is looking for something that does not correspond one to one.

The App Store app and a window of the site are not the same thing

Assuming the consumer app is the right target and the Mac meets the version requirement, there is still a choice between installing it and using the site in a window of its own. They differ in ways that matter.

A Mac App Store app is sandboxed and updated through the App Store. It handles system integration properly: notifications, the Dock, keyboard media keys, the share sheet. It is also a fixed thing. What it can do is what the developer shipped.

A site opened in a window of its own inherits the browser it was built from. Extensions stay active, the password manager works, the sign in that already exists carries over, and a second account is a second profile rather than a second install. That last point is the one that decides it for a lot of people, because the version most needed at work is exactly the one with no App Store listing.

The two can coexist. The consumer app for personal use, a standalone window for the work surface, and the editor extension for code, is a coherent setup where each piece is doing the thing it is actually good at. Keeping them visually distinct helps: different names in the Dock, different icons, so the app switcher does not present two entries that read the same at a glance.

Choosing between them without installing everything

Three questions settle it, and they are quick.

What the macOS version is. The floor for the App Store app is macOS 14.0, and there is no workaround. Check it in the Apple menu under About This Mac before spending time on anything else, because a machine on macOS 13 has exactly one option and the rest of the decision disappears.

Which account signs in. If the answer is a work or school address, the App Store app is not the product being paid for, and a window on the Microsoft 365 address is the closer fit. If it is a personal Microsoft account and the Mac runs macOS 14 or later, the App Store app is the simplest path and takes a minute.

Whether extensions or a specific browser profile matter. A password manager extension, a translation extension, or a profile already signed into the right tenant are all reasons a browser based window wins, and none of them are available inside a sandboxed App Store app. The Features page lays out what a standalone window keeps from the browser underneath it, which is precisely the list that decides this question. For the work surface specifically, a window built on an existing browser profile means the tenant sign in and its policies keep working, because nothing about the session changed. The Supported services list shows which of these web surfaces are commonly given their own window, and the Guide covers the setup end to end.

What to change first

Check the macOS version, then check which account is going to sign in. Those two answers pick the route, and everything else follows. If the account is a work account, or the Mac is on an older macOS, stop looking for a download and put the web surface into a window of its own instead, which is what Kagemusha is for.