Overview
The Robost browser extension runs inside Chrome, Edge, and Firefox (Manifest V3) and connects every enrolled device to your organization’s Robost dashboard. It operates silently in the background without interrupting employees while giving your security and compliance team full visibility into AI application usage.
What the extension does
Section titled “What the extension does”- Observes AI app usage. The extension detects when employees visit supported AI tools (ChatGPT, Gemini, Claude, and others) and records the interaction context needed to evaluate policy compliance.
- Enforces policies. Configured scenarios are pushed to the device at enrollment and kept in sync. When a policy condition is met, the extension generates an alert payload locally and queues it for delivery.
- Surfaces alerts. Alerts are flushed to the Robost backend in real time and retried automatically every five minutes if the device is temporarily offline. Your team sees them in the Alerts dashboard immediately after submission.
Supported browsers
Section titled “Supported browsers”| Browser | Engine | MV3 |
|---|---|---|
| Google Chrome | Chromium | Yes |
| Microsoft Edge | Chromium | Yes |
| Mozilla Firefox | Gecko | Yes (Firefox MV3) |
Update channel
Section titled “Update channel”The extension is distributed through a self-hosted Google Cloud Storage bucket and updated via Chrome’s standard extension update mechanism. Chrome polls for new versions approximately every five hours. Admins can force an immediate update from chrome://extensions by clicking Update. Version numbers are monotonically increasing; Chrome will not downgrade an enrolled device.
Managed deployment paths
Section titled “Managed deployment paths”For organization-wide rollout, choose the path that matches your MDM:
- Google Workspace — force-install via Google Admin Console Chrome policy
- Microsoft Intune — deploy via Intune configuration profile
- Jamf Pro — push via Jamf computer configuration profile
Credential model
Section titled “Credential model”Each device authenticates to the Robost backend using an enrollment token. Tokens can be pushed automatically through managed storage (MDM) or entered manually by the user on the extension’s options page. See Enrollment & Device Credentials for the full credential lifecycle.
Troubleshooting
Section titled “Troubleshooting”If the extension appears installed but is not reporting data, see the Troubleshooting page for a symptom-by-symptom diagnostic guide.