Skip to main content
The browser extension is the fastest route to meaningful coverage, because most AI use happens in a browser tab. Deploy this first.

​
What it is

A Manifest V3 extension for Google Chrome and Microsoft Edge, shipped as two builds from one codebase. It injects a content script into supported AI sites; when a user hovers a text input, an Analyze affordance appears, and the resulting suggestion must be explicitly accepted before any text changes.

​
Permissions it requests

Your security review will ask about this, so here it is in full.
Note what is not requested: no tabs (full tab metadata), no webRequest, no cookies, no <all_urls>, and no history.
The manifest also contains localhost entries used by development builds. Verify you are deploying a production build — production builds emit only the production configuration and strip the development config entirely.

​
Sites it activates on

The extension is active on the major assistants and a long tail of AI-adjacent tools:
Anything outside this list is not covered by the extension. If your users work in a native desktop app — the ChatGPT desktop client, Slack, Outlook — you need the macOS or Windows agent for that traffic.

​
Architecture

All network calls and token handling are confined to the background service worker. The content script never holds a token.

​
Deploying it

1

Pilot with a manual install

Have your pilot group install from the Chrome Web Store or Edge Add-ons listing. Confirm sign-in works against your tenant and that the Analyze affordance appears on ChatGPT.
2

Confirm the suggestion types

In Settings, review the suggestion categories enabled for your organisation. Toggle off anything noisy for your environment before widening the rollout.
3

Force-install via MDM

Push the extension ID through your MDM’s Chrome/Edge managed policy. Exact payloads for Intune, Jamf Pro, Kandji, and JumpCloud are on the MDM rollout page.
4

Verify coverage

Check the console’s deployment view for check-ins, and reconcile against your MDM device roster to find machines where the policy applied but the extension never phoned home.

​
Testing an unpacked build

For pre-release validation you can side-load a build directly.
  1. Go to chrome://extensions/
  2. Enable Developer mode
  3. Click Load unpacked
  4. Select the dist-chrome directory
Side-loaded extensions are not auto-updated and are disabled by policy in many managed fleets. Use this for validation only, never for production rollout.

​
Pages the extension exposes to users

​
Environments

Builds are environment-aware. A dev build and a prod build embed different API endpoints, Auth0 credentials, and analytics keys, and a production build contains only the production block — the development configuration is not shipped. When you receive a build for deployment, confirm with whoever produced it that it is the production target for the correct browser.