Docs

Connect

The browser extension

See which AI chat tools people use in Chrome and Edge, how much, and who pays for two. It counts messages; it never reads what anyone types.

Most of a company's AI use never touches an API key: people open ChatGPT, Claude, Gemini or Copilot in a browser tab, on seats the company pays for every month. The extension shows who uses which chat tool, how often and with which model. That is where seat savings come from: unused seats, people paying for two overlapping tools, and light users on an expensive plan.

Important. The extension is a signal, never an audit. A person can disable it, it sees only browsers where it is installed, and the chat sites change their pages without notice. No bill or finding rests on it alone. For exact chat usage, connect the vendor's admin data (Claude Enterprise, Microsoft 365 Copilot) under Setup.

#What it records, and what it never does

Recorded, for each message sent on a supported site Never recorded
which tool: ChatGPT, Claude, Gemini, Copilot, DeepSeek or Kimi what the person typed, or the answer
the model picked, when the site says so the conversation's real id: it is replaced by a salted hash, so conversations can be counted, never looked up
when, and the message's length in characters any other website: the extension can only observe the AI sites it lists
how long the answer took, and which features were on (such as web search) the page itself: there is no content script, so it never reads or changes what is on screen
the work account the browser profile is signed in with the query string or body of any request

These promises are enforced in code and checked by tests:

  • The prompt text is read only to count its characters. A test feeds the extension a real chat request and checks that no word of the prompt and no conversation id comes out.
  • IA4AI stores only the declared fields. A tampered extension that sent text anyway would have it dropped on arrival.
  • The extension's permissions are pinned by a test: adding one, or <all_urls>, fails the build.
  • The extension's popup shows the person everything above, the connection status and today's count.

Warning. Tell people before you deploy it. In the EU, monitoring work tools requires telling the people monitored, and sometimes consulting a works council. IA4AI provides a one-page staff notice, and the popup text is a starting point. A workspace can also store people under a pseudonym instead of their email: see Privacy and your data.

#The extension key

The extension has its own key, iax_…. It can fetch the extension's settings and send usage events into your workspace, and nothing else: it cannot read a report, a case or another key, so it is safe on every laptop. Create it under Setup → Browser extension. It is shown once. Creating a new one disconnects every browser on the old one.

#Install it for yourself

  1. Install the ODUX-IA4AI extension from the Chrome Web Store and click Add to Chrome. Edge installs it from the same page.
  2. Click the extension's icon, then Settings. The address is filled in: paste the extension key and click Save and test.
  3. Send a message in ChatGPT or Claude, then click Check my connection on your Connect page.

To try a version before it reaches the store, download https://ai.odux.io/app/extension.zip, unzip it, and load the folder with Load unpacked on chrome://extensions (Developer mode on).

#Roll it out to a company

Browser policy installs the extension on every managed Chrome or Edge and enrols it, with nobody typing anything.

  1. Install: add the extension to ExtensionInstallForcelist as ffppgeghdjiecjnkcnljkghcanmhdpgb;https://clients2.google.com/service/update2/crx (its Chrome Web Store ID and the store's update address). In the Google Admin console: Apps and extensions → Add from Chrome Web Store, then Force install.
  2. Enrol: set the extension's managed policy. In the Google Admin console it is the extension's Policy for extensions box; in Intune a custom configuration under Software\Policies\Google\Chrome\3rdparty\extensions\ffppgeghdjiecjnkcnljkghcanmhdpgb\policy (or Microsoft\Edge).
Extension policy
{
  "serverUrl": "https://ai.odux.io/app",
  "extensionKey": "iax_…"
}

With the policy present, the extension's settings are locked and say that IT set it up. People should be signed in to the browser with their work account, so usage is tied to the right seat; a profile that is not signed in is still counted, as unknown.

#What you see

The Chat apps screen and GET /report/browser show, for the period:

  • per tool: how many people used it, messages, sessions and models;
  • per person: each tool they used, with messages and active days;
  • overlap: people active on two or more chat tools, candidates for keeping one subscription;
  • light use: people active on a tool on three days or fewer, candidates for a cheaper plan or no seat;
  • typical answer times, how often each feature was on, and messages by hour of the day.

#When a site changes

Which request counts as "a message was sent" is decided by rules on IA4AI's server, not in the extension, and every extension fetches them again each hour. When a vendor changes its site, the rule is fixed on the server and every browser picks it up within the hour, with no new release. A request on a supported site that no rule recognises is kept only as its shape (method, site and path with every id removed), never counted as usage, so a broken rule shows up instead of silently counting nothing.

If one tool's numbers drop to zero for everyone at once, that is almost always the vendor changing its site, not people stopping. Tell us and we fix the rule.

#Limits

  • Browsers only. Desktop apps (ChatGPT for Mac, Claude Desktop, Copilot in Windows) and phones are not covered: the vendors' admin data covers those.
  • Copilot is counted per chat session, not per message.
  • The extension reports only to https://ai.odux.io.