Verifying Deployment
Complete this checklist on a managed device after pushing the extension policy. A workstation is not considered fully connected until force-install, enrollment, and event delivery are all confirmed.
Complete this checklist on a managed device after pushing the extension policy. A workstation is not considered fully connected until force-install, enrollment, and event delivery are all confirmed.
Layer 1: Policy applied
Chrome / Edge / Brave:
- Open
chrome://policy(oredge://policy,brave://policy). - Confirm
ExtensionInstallForcelistcontains the AgentKeeper entry. - Confirm the managed config keys (
orgApiKey,userEmail) appear under the extension's policy section.
If the policy section is missing, the MDM profile has not applied yet. Wait for the next policy sync or trigger a manual sync in your MDM console.
Firefox:
- Open
about:policies. - Confirm
ExtensionSettingscontainshelp@rad.securitywithinstallation_mode: force_installed.
Layer 2: Extension installed and paired
Chrome / Edge / Brave:
- Open
chrome://extensions. - AgentKeeper appears with the badge "Installed by your administrator" and cannot be removed.
- Click the AgentKeeper toolbar icon. The popup reads Paired, not "Unpaired" or "Connect".
Firefox:
- Open
about:addons. - AgentKeeper appears under Extensions with "Installed by your organization".
- Extension popup reads Paired.
If the popup reads "Unpaired": the managed config was not delivered correctly. Re-check the orgApiKey value in your MDM policy and confirm there are no JSON formatting errors.
Layer 3: Device appears in AgentKeeper
- Open the AgentKeeper dashboard.
- Go to Inventory → Workstations.
- The managed machine appears with:
installMethod: browser_extension- The correct user bound (if
userEmailwas provided in managed config) - A green status indicator
If the device does not appear within 5 minutes of enrollment:
- Check the org API key is correct and has not been revoked (Settings → Access → API keys).
- Confirm the machine can reach
https://www.agentkeeper.dev(outbound HTTPS).
Layer 4: Events flowing
- On the managed machine, open claude.ai and send a test prompt.
- In the AgentKeeper dashboard, go to Activity.
- A new event appears with source
browser_extensionwithin seconds.
If no event appears after 60 seconds:
- Confirm the extension is paired (Layer 2).
- Open the extension's Options page → Dev mode → check the event log for errors.
- Check
chrome://extensions → AgentKeeper → Service Worker → Inspectfor console errors.
Extension ID reference
The extension ID is required when writing MDM policies.
- Chrome / Edge / Brave / Arc:
lllalmnahkbikalapoancgfkiegfoiim(one Chrome Web Store ID shared across all Chromium browsers). To confirm on a device:chrome://extensions→ AgentKeeper → Details → Extension ID. - Firefox:
help@rad.security
Common issues
| Symptom | Likely cause | Fix |
|---|---|---|
Extension not appearing in chrome://extensions | Policy not yet applied | Trigger MDM sync; wait up to 5 min for Chrome to pick up the policy |
| Popup reads "Unpaired" | orgApiKey missing or wrong in managed config | Verify the key in your MDM policy; re-push |
| Device not in Workstations dashboard | Backend unreachable or key revoked | Check outbound HTTPS to www.agentkeeper.dev; verify key is active |
| User not bound to device | userEmail not in managed config | Add userEmail with MDM variable substitution and re-push |
| Wrong user bound | Email variable resolved incorrectly | Check MDM variable output; device re-enrolls with correct email on next Chrome restart |