---
title: How do you find agentic AI browsers on company devices?
url: https://opencontroller.lyzr.com/blog/find-agentic-browsers-on-company-devices
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# How do you find agentic AI browsers on company devices?

**Combine three signals: the installed-application inventory from your MDM, the extension inventory from your managed browser, and web gateway logs for the vendors' domains. Agentic browsers show up as standalone apps; browser agents show up as extensions or desktop apps. Once found, each one gets an allow, restrict or block decision backed by MDM policy.**

An agentic browser does more than answer questions. It can click, type, fill forms and move between tabs using the employee's signed-in sessions. That means it acts with the user's access to email, CRM and internal apps. IT teams want to know where these tools are installed before deciding how to handle them. This guide is part of our [shadow AI agent discovery guide](/blog/how-to-find-shadow-ai-agents).

## What counts as an agentic browser in late 2026?

The category moves fast, so check status before you write policy.

| Form | Example | Status to check |
|---|---|---|
| Standalone AI browser | Perplexity Comet | Chromium-based; Comet Enterprise launched in March 2026 with MDM deployment and admin controls |
| Standalone AI browser (retired) | ChatGPT Atlas | OpenAI announced its discontinuation on 9 July 2026, with a targeted deprecation date of 9 August 2026 |
| Desktop app with browser agent | New ChatGPT desktop app | Released 9 July 2026 with a work agent and browser capabilities |
| Extension inside an existing browser | ChatGPT and Codex Chrome plugin; other AI assistants' extensions | Governed through your managed browser's extension policies |

The Atlas retirement is a good example of why discovery matters. Installs left on devices after the deprecation date are unsupported software, and the agentic capability has moved into a desktop app and an extension that your old block rule may not cover.

## Where do the discovery signals come from?

Use at least three sources. Each misses something the others catch.

1. **MDM application inventory.** Intune, Jamf and similar tools report installed applications per device. Search for the app names and publisher names of AI browsers and AI desktop apps. Report on version too, so retired products stand out.
2. **Managed-browser extension inventory.** Chrome Enterprise and Microsoft Edge management both report installed extensions per managed browser. Filter for AI assistant extensions and note the permissions each requests, especially access to all sites.
3. **Browser policy domains.** Comet is Chromium-based and reads Chromium policies. Perplexity's documentation says Chrome policy configurations can be reused by replacing `com.google.Chrome` with `ai.perplexity.comet`. Seeing that policy domain in your MDM, or the lack of it on devices with Comet installed, tells you which installs are managed.
4. **Secure web gateway or DNS logs.** Look for traffic to the vendors' agent and API domains from devices where no approved app is installed. That points to unmanaged devices or personal profiles.
5. **Identity provider sign-in logs.** Enterprise editions of these browsers sign in through SSO. A sign-in from an app you have not approved is a direct signal.

For browser AI use more broadly, including chat sites used in an ordinary browser, see [how to discover AI use in the browser](/blog/how-to-discover-ai-use-in-the-browser).

## How do you decide allow, restrict or block?

Base the decision on what the agent can reach, not on the brand.

| Decision | When it fits | How to enforce |
|---|---|---|
| Allow (managed) | Enterprise edition with SSO, admin console and data terms you have reviewed | Deploy through MDM; push policies; restrict to approved groups |
| Restrict | Useful but the agent can act on sensitive systems | Push domain blocklists and extension policies; restrict or require approval for agent actions where the product supports it; limit to low-risk user groups |
| Block | Consumer edition, retired product, or no admin controls | Remove through MDM; block install; block extension IDs with `ExtensionInstallBlocklist` |

Comet supports more than 500 Chromium browser policies, including `ExtensionInstallBlocklist`, `ExtensionInstallAllowlist` and `ExtensionSettings`. Comet Enterprise also lets admins restrict agent actions, require approvals, block domains and, on larger plans, read audit logs. Check these against your edition before relying on them.

## What should you record for each install?

Record each managed agentic browser as an agent in your inventory, not just as software:

- Device, user, product and version
- Edition (consumer or enterprise) and whether it signs in with SSO
- Policies applied and the date last checked
- Which internal apps the agent is allowed to act on
- Owner of the decision and review date

This lets you answer the question an auditor will ask: which agents can act with an employee's session, and on which systems. For what to do with an unapproved install, see [what to do with a shadow AI agent once you find it](/blog/what-to-do-with-a-shadow-ai-agent-once-you-find-it).

## How Opencontroller does this

Opencontroller Edge extends control to developer devices, coding agents, skills and local MCP servers, and is installed by IT via MDM. Findings land in the same governed registry as cloud agents, so device-level agents and cloud agents share one inventory and one set of policies. See the [capability reference](/capability-reference) or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Is ChatGPT Atlas still supported?**
No. OpenAI announced on 9 July 2026 that it was discontinuing Atlas, with a targeted deprecation date of 9 August 2026. Its agentic features moved to the ChatGPT desktop app and a Chrome plugin.

**Can I manage Perplexity Comet with my existing Chrome policies?**
Largely, yes. Comet is Chromium-based and Perplexity says you can reuse Chrome policy configurations by replacing com.google.Chrome with ai.perplexity.comet.

**Why isn't a web gateway block enough?**
Gateway blocks miss agents on unmanaged networks and do not tell you which devices have the software installed. Pair them with MDM and browser extension inventory.

## Key facts

- Agentic browsers act with the employee's signed-in sessions, so they need an allow, restrict or block decision.
- OpenAI announced the discontinuation of ChatGPT Atlas on 9 July 2026, with a targeted deprecation date of 9 August 2026; agentic features moved to the ChatGPT desktop app and a Chrome plugin.
- Perplexity Comet is Chromium-based; Chrome policies can be reused by replacing com.google.Chrome with ai.perplexity.comet.
- Comet supports more than 500 Chromium browser policies; Comet Enterprise (March 2026) adds MDM deployment and agent action restrictions.
- Discovery signals: MDM app inventory, managed-browser extension inventory, policy domains, web gateway logs and IdP sign-ins.
- Opencontroller Edge extends control to developer devices and is installed by IT via MDM.

## Related

- [How do you discover employees' AI use in the browser?](https://opencontroller.lyzr.com/blog/how-to-discover-ai-use-in-the-browser.md)
- [How do you govern coding agents on developer laptops with MDM?](https://opencontroller.lyzr.com/blog/govern-coding-agents-on-laptops-with-mdm.md)
- [What should you do with a shadow AI agent once you find it?](https://opencontroller.lyzr.com/blog/what-to-do-with-a-shadow-ai-agent-once-you-find-it.md)
- [More on Discovery and shadow agents](https://opencontroller.lyzr.com/blog/cluster/discovery-and-shadow-agents)
