Browser Extension

The AgentKeeper browser extension collects supported AI web sessions alongside the desktop runtime. Events flow into AgentKeeper Activity and policy decisions when a site adapter is enabled and the browser has the required host permission.

Supported browsers

Chromium family (Chrome, Edge, Brave, Arc, Dia, Vivaldi) shares a single Chrome Web Store extension ID: lllalmnahkbikalapoancgfkiegfoiim. On macOS, deploy to multiple Chromium browsers from one .mobileconfig. See macOS: Multi-browser.

Firefox uses a separate signed XPI with its own extension ID (help@rad.security).

What the extension captures

The extension patches window.fetch, XMLHttpRequest, and EventSource at page execution time. No TLS interception, no proxy CA, no network configuration required.

Captured per supported AI session:

• Prompts sent to the AI
• Model responses (full or streaming)
• Tool definitions, tool calls, and tool results
• Session and model metadata (model name, timestamp, session ID)

Pre-submit policy check: Before a supported prompt request is sent, the extension dispatches a preflight check to AgentKeeper. If the backend returns warn or block, a Shadow DOM intervention appears and the page request is aborted. The user sees the verdict; a blocked request does not reach the AI provider.

Supported sites: claude.ai, ChatGPT (chatgpt.com / chat.openai.com), Gemini (gemini.google.com), and Perplexity (perplexity.ai).

Supported platforms

Frequently asked questions

How does the extension connect to AgentKeeper?

The extension is enrolled with an org API key. In a zero-touch enterprise deployment, the key is delivered via chrome.storage.managed (an MDM-provisioned policy). The extension reads it on startup and calls POST /api/v1/extension/enroll-org at the configured AgentKeeper API root to self-pair without user interaction.

For individual developer installs, a device-code pairing flow is available from the extension's Options page.

Does the extension send raw browser traffic?

No. The extension parses structured AI protocol fields from fetch and XHR responses. It does not capture raw request bodies, cookies, authorization headers, or traffic from any site other than the configured AI providers. A local redaction engine strips PII and secret patterns before events leave the extension.

How resource-intensive is the extension?

Events are queued in IndexedDB and drained every 30 seconds via a chrome.alarms callback. The service worker wakes only when needed and does not run a persistent background process. Footprint is negligible under normal usage.

What happens if the backend is unreachable?

The extension queues events locally and retries. The queue holds up to 5,000 events or 50 MB, with the oldest entries dropped first. Backend unavailability does not block prompts; the pre-submit check fails open.

Can the extension be installed without MDM?

Yes. Developers can install the extension from the Chrome Web Store or Firefox AMO and pair it manually via the Options page. Enterprise IT teams typically use MDM force-install to ensure coverage and disable manual removal.

Can a user disable or uninstall the extension?

Force-installed extensions cannot be removed by the user. The browser shows an "Installed by your administrator" badge. Removing the MDM policy entry allows uninstallation on the next policy sync.

Next steps

• About deployment: Zero-touch enrollment overview and managed configuration schema
• Windows: Intune: Force-install through Intune with managed configuration
• Windows: Group Policy: Registry-based deployment
• macOS: Jamf: Jamf configuration profile and managed preferences
• macOS: Iru/Kandji: Iru/Kandji Library Item and managed preferences
• macOS: Intune: Intune shell script and property list profile
• Firefox: policies.json for all platforms
• Verifying deployment: Confirm force-install, enrollment, and first events

Deploy the extension

Force-install the extension, deliver managed config, and validate pairing plus first events.