Wake · Osabee

AI browser inventory: which AI runs in your team’s browsers?

An AI agent installed in a browser works inside an already authenticated session. To your CRM, your admin panels and your mail, it is the employee — and server-side logs show no difference at all.

Free. No account. No site access, no network connection.

Wake popup showing detected AI agents

The blind spot of every AI inventory

AI governance and SaaS discovery tools find accounts through SSO, expenses and network traffic. A browser extension someone installed with a personal account passes through none of those channels. It is invisible to all of them.

ISO/IEC 42001 applies to organisations that use AI, not only to those that build it — and the AI system inventory is where audits are won or lost. Shadow AI in the browser is the part of that inventory nobody can currently see.

What Wake does

Finds them

Lists the AI tools installed and classifies them by what they can actually do, not by what they claim.

Shows the reach

Which ones can act inside pages, read session cookies, drive the browser, or were installed outside the store.

Tracks change

Compares against the previous scan and tells you what appeared since.

Exports evidence

CSV with the columns an AI system register asks for: purpose, access scope, install origin, detection date.

What Wake does not do

Wake requests access to no website. It injects no code into pages. It makes no network connections. It has no servers and collects no data. Two permissions: read the list of installed extensions, and store scan history locally. An extension that flags others for the permissions they request cannot afford to request more than they do.

Every browser in one list

The free scan covers one browser. If you need the inventory across a whole team — every device in one list, alerts when a new agent appears, a single export for the auditor — tell us and we will come back to you when it is ready.

Guides

Guides: shadow AI, browser extensions and AI inventories