Removal runbook for IT
How to Uninstall AI Browsers from Managed Macs and PCs
Comet, Atlas, Dia, BrowserOS and agent extensions are already on some of your devices. Blocking new installs does not remove them, and dragging an app to the bin leaves its logins behind.
This runbook takes you through four phases: find every copy, remove it, stop it coming back and clean up what it left.
The runbook
- 1FindBundle IDs, package IDs, process names, extensions
- 2RemoveIntune, winget, Jamf, Store uninstall assignments
- 3PreventDomains, app control, extension blocklists
- 4Clean upSessions, app connections, profiles, passwords
Next step
AI Agent Blocklist: the identifiers and domains to find and keep out AI browsers
Bundle IDs, Windows package IDs, process names and extension IDs of AI browsers and agents, plus their domains, updated every day for your MDM, firewall and DNS filter.
From $99 a month for one organisation
Why AI browsers are harder to remove than other apps
An AI browser is a full browser with an agent inside. It holds sessions, passwords and history, it updates itself, and it often installs without admin rights.
Per-user installs
Many browsers can install into the user's own profile. A device scan that only looks at Program Files or /Applications misses them.
Updaters
Comet ships an updater component and Atlas had an update helper. Leftover helpers keep running if you only delete the main app.
Imported logins
AI browsers offer to import passwords and sessions from Chrome at first run. BrowserOS, for example, imports Chrome logins in one click.
Agents as extensions
Claude in Chrome and similar agents live inside Chrome, Edge or Brave. Uninstalling apps does nothing to them.
Who is most exposed
- Staff with access to finance, HR or customer systems in the browser
- Developers, whose AI browser may also talk to coding agents
- Admins and executives signed in to many services at once
- Shared or lab machines where one install serves many users
Signs a device needs this runbook
- A second browser in your app inventory that you never deployed
- DNS lookups to AI browser and agent domains
- A browser process running from a user profile folder
- An extension with access to all sites and a side panel
The removal runbook at a glance
Do the phases in order. Removing first and blocking later means users reinstall in between; blocking first without removal leaves running copies with live sessions.
- Phase 1: Find
Build the list of affected devices and users
Search MDM inventory by identifier, not by app name. Names change, IDs rarely do. Include extensions in all Chromium browsers.
- Phase 2: Remove
Uninstall in the right context
System-wide installs need a system task; per-user installs need a task that runs as the user. Quit the browser first.
- Phase 3: Prevent
Block reinstalls on three layers
Network (domains), device (app control rules) and browser (extension blocklist). One layer alone is easy to step around.
- Phase 4: Clean up
Close what the browser opened
Revoke sessions and app connections, remove leftover profiles, and rotate passwords for accounts the AI browser held.
Phase 1: find every AI browser and agent extension
These are a few of the identifiers we track for the browsers on this page. Our full list holds 5,300+ identifiers across AI browsers, agent apps, extensions and coding agents.
| Tool | macOS | Windows | Process name |
|---|---|---|---|
| Comet | ai.perplexity.comet ai.perplexity.CometUpdater | winget Perplexity.Comet Store XPFFVLPJRVQTKM | Comet |
| ChatGPT Atlas | com.openai.atlas com.openai.atlas.update-helper | Not applicable | ChatGPT Atlas |
| BrowserOS | Homebrew cask browseros | winget BrowserOS.BrowserOS | BrowserOS |
| Dia | Desktop app for macOS and Windows. Its identifiers are in our download files. | In our files | |
| Claude in Chrome | Chrome Web Store extension ID fcoeoabgfenejglbffodgkkbkcdhcgfn, also installable in Edge and Brave | Runs inside the browser | |
Windows: is Comet installed for this user?
winget list Perplexity.Comet -e
macOS: where is ChatGPT Atlas?
mdfind "kMDItemCFBundleIdentifier == 'com.openai.atlas'"
Intune
Use the Discovered apps report and filter by name and publisher. Check the current admin console for its location.
Jamf Pro
Build a smart computer group from application inventory, then scope removal policies to it.
Browsers
Pull installed extension IDs from Chrome and Edge management reports and match them to our extension list.
Inventory is a job of its own. For a wider view of every agent in the company, see our page on building an AI agent inventory.
Phase 2: uninstall on Windows and macOS
Quit the browser, remove the app in the context it was installed in, and confirm with the same detection query you used in phase 1.
- In the Intune admin center go to Devices, Scripts and remediations, Platform scripts, Add, Windows 10 and later.
- Upload a script that calls winget. Keep "Run this script using the logged on credentials" at Yes, so per-user installs are found.
- Assign it to the device group from phase 1. Scripts retry three times on failure and time out after 30 minutes.
- For Store installs, add the app under Apps, All Apps, Create, Microsoft Store app (new), and assign it as Uninstall.
Platform script: remove Comet and BrowserOS
winget uninstall Perplexity.Comet -e -h -s winget winget uninstall BrowserOS.BrowserOS -e -h -s winget
- Create a policy with a script, scoped to the smart group from phase 1.
- The script finds the app by bundle ID, quits the process and removes the app bundle wherever it sits.
- Run it at check-in, once per computer, and again after a week to catch late installs.
- Kandji, Mosyle and Intune can run the same shell script through their own script features.
Policy script: remove ChatGPT Atlas
APP=$(mdfind "kMDItemCFBundleIdentifier == 'com.openai.atlas'" | head -n 1) pkill -x "ChatGPT Atlas" [ -n "$APP" ] && rm -rf "$APP"
Test every script on one device first. Spotlight must be indexing the disk for mdfind to find the app, and winget must be present for the signed-in user. A query that finds nothing is not proof that nothing is installed.
For the policy side of Intune, including blocking AI sites and apps beyond browsers, see how to block AI tools with Intune.
How to uninstall Perplexity Comet, ChatGPT Atlas, Dia and Claude in Chrome
Each tool needs a slightly different removal. The cards below cover what is specific to each one; the dedicated pages cover blocking in depth.
On Windows it can come from a direct download, winget or the Microsoft Store, so check all three. On Macs, remove the app and its updater.
Perplexity.Comet
OpenAI retired Atlas: it was scheduled to stop working on 9 August 2026, and its agent features moved into ChatGPT and Codex. Installed copies and their data stay until you remove them.
com.openai.atlas
Dia is available for macOS and Windows and offers a Dia for Work plan with SSO and admin tools. If you licence it, remove only unmanaged copies.
Identifiers in our files
Put the ID in ExtensionInstallBlocklist for Chrome, Edge and Brave. Installed copies are disabled at once, and users cannot turn them back on.
fcoeoabgfenejglbffodgkkbkcdhcgfn
An open-source agentic browser for macOS, Windows and Linux. It can expose an MCP server that coding agents use to drive it, so check developer machines first.
BrowserOS.BrowserOS
After Atlas, OpenAI points users to the ChatGPT desktop app for browser-based agent work. Decide whether it is approved; if not, remove it with the same runbook.
OpenAI.ChatGPT
Phase 3: stop AI browsers coming back
Users who liked an AI browser will try again. Each layer below stops a different route back, and together they cover home networks, new downloads and new extensions.
Block AI browser download pages and service domains in your firewall, secure web gateway or DNS filter. A browser that cannot reach its back end cannot run its agent.
Our list ships as a plain domain list, hosts file, PAC file and firewall external list. See blocking AI agents at the firewall.
Create an AppLocker deny rule with a publisher condition for each signed AI browser. Packaged apps from the Store need a packaged app rule, which always uses publisher conditions.
The "Turn off the Store application" policy stops users installing arbitrary Store apps. It does not affect winget, so keep the deny rules too.
In Jamf Pro go to Computers, Restricted software, New. Enter the exact process name, such as Comet or ChatGPT Atlas, tick Kill Process and scope it to all managed Macs.
For a process inside an app bundle, Jamf suggests the full bundle name ending in .app. Use ps -acx on a test Mac to read the exact name.
Keep agent extension IDs in ExtensionInstallBlocklist in every Chromium browser you allow. For Macs managed with Jamf, see blocking Chrome extensions with Jamf.
New AI browsers appear every month. App control rules for known names cannot catch a browser released next week; a list that is updated every day can.
Phase 4: clean up what the AI browser left behind
Removing the app ends the agent. It does not end the sessions, tokens and copies of data it created while it ran.
Export first. Let users export bookmarks as an HTML file before removal. Atlas users were told that bookmarks, tabs and history do not move across on their own.
Remove leftover profiles. App removal often leaves the browser profile in the user's folder, with history, cookies and saved passwords.
Revoke app connections. If users linked mail, calendar or file storage to the AI service, review consented apps in your identity provider and revoke the grants.
Sign out the AI account. Ask users to sign out of the AI service on removed devices. If your company has a workspace with that vendor, remove device sessions there.
Rotate key passwords. Where a user imported passwords into an AI browser, rotate those for admin consoles, finance systems and shared accounts.
Check helper processes. Run the phase 1 query again a few days later. Updaters, helpers and a second user's copy show up here.
Log the change. Record which devices were cleaned and when. Auditors will ask how you enforced the AI policy.
Offer the approved path. Point users to the AI tools you do allow, so removal does not turn into a hunt for the next unapproved browser.
Six mistakes that make AI browsers come back
Failed clean-ups usually come down to the same few causes. Check your plan against this table before you start phase 2.
| Mistake | What happens | Fix |
|---|---|---|
| Uninstall runs only as SYSTEM | Copies installed in a user's profile stay, and the report still says success. | Run the removal in the user's context as well, or loop through user profiles. |
| Searching by app name | Renamed, beta or localised builds are missed. | Search by bundle ID, package ID and process name. |
| Blocking weeks after removing | Users reinstall in the gap, often from home. | Switch on the network and app control blocks on the same day as removal. |
| Deleting the app, not the helpers | Updaters or helper processes keep running and may fetch a new copy. | Re-run detection for helper IDs a few days later. |
| Only cleaning Chrome | The same agent extension lives on in Edge or Brave. | Apply the extension blocklist to every Chromium browser you allow. |
| No word to users | Tickets, frustration and quiet workarounds. | Send a short notice and point to the AI tools you approve. |
What to tell users before you remove their AI browser
A short message avoids tickets and quiet reinstalls. Adapt this one to your policy and send it a few days before phase 2.
Message to staff
From next week we will remove AI browsers such as Comet, Dia and BrowserOS, and agent extensions such as Claude in Chrome, from company devices.
These tools can act on websites where you are signed in, and that is not yet allowed under our AI policy. Please export any bookmarks you want to keep before Friday.
You can keep using the approved AI tools listed on the intranet. If you need an agent for your work, ask IT and we will review it.
Run the runbook with lists that stay current
Every phase depends on identifiers and domains. We maintain them so your queries, app control rules and blocklists cover the AI browsers released after you wrote them.
Every entry has a tool name, category, identifier type and risk grade. See what the AI Agent Blocklist contains.
From $99 a month for one organisation
- macOS bundle IDs and process names of AI browsers and agent apps, for Jamf and Intune
- Windows package IDs and process names for detection and app control
- Chrome, Edge and Firefox extension IDs of agent extensions, as policy files
- 2,600+ AI agent domains for firewalls, DNS filters and PAC files
- CSV and JSON with every column, including the risk grade
- Daily updates; download access set up within one business day
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Questions about removing AI browsers
How do I uninstall Perplexity Comet from company PCs?
Run winget in the user's context, for example with an Intune platform script set to run with the logged-on credentials: winget uninstall Perplexity.Comet -e -h -s winget.
If it came from the Microsoft Store, add the Store app XPFFVLPJRVQTKM in Intune and assign it as Uninstall. Then block reinstalls.
How do I uninstall ChatGPT Atlas from a Mac?
Quit the ChatGPT Atlas process, find the app by its bundle ID com.openai.atlas and remove it, then remove the user's leftover Atlas profile data after any bookmarks are exported.
On managed Macs, run this as a Jamf Pro policy script and keep a restricted software record for the process name.
OpenAI retired Atlas. Do I still need to remove it?
Yes. Atlas was scheduled to stop working on 9 August 2026, but retirement does not uninstall anything. The app and its local browser data, such as history and cookies, stay on the Mac until you remove them.
How do I uninstall the Dia browser?
Dia is available for macOS and Windows. Remove it like any other desktop app: quit it, uninstall it with your MDM or the operating system, and clean up the user's profile data. If your company has Dia for Work, remove only the unmanaged copies.
How do I uninstall Claude in Chrome for all users?
Add the extension ID fcoeoabgfenejglbffodgkkbkcdhcgfn to the ExtensionInstallBlocklist policy in Chrome, and the same ID in Edge and Brave. Installed copies are disabled at once and users cannot switch them back on.
Does uninstalling an AI browser delete the user's data?
Not always. App removal often leaves the browser profile with history, cookies and saved passwords. Export what the user needs, then remove the profile and revoke any sessions or app connections the AI browser created.
Why does an AI browser come back after I uninstall it?
Usually because the user downloads it again, or because a per-user copy in another profile was never removed. Block the download and service domains, add an app control rule, and keep a detection rule that alerts on the bundle ID, package ID or process name.
Perplexity and Comet are trademarks of Perplexity AI, Inc. ChatGPT, ChatGPT Atlas and Codex are trademarks of OpenAI. Dia is a trademark of The Browser Company of New York. Claude is a trademark of Anthropic, PBC.
Chrome is a trademark of Google LLC. Microsoft, Windows, Edge and Intune are trademarks of Microsoft Corporation. macOS is a trademark of Apple Inc. Jamf Pro is a trademark of Jamf. BrowserOS, Brave, Kandji, Mosyle and other product names are trademarks of their owners.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.