Upgrade and reset
Upgrade the console and extension together, and reset a browser whose enrollment needs to start over.
On this page
The console accepts reports only from its own extension version. There are no adapters for older versions, so the console and the extension come from the same release and are upgraded together.
Upgrade
Plan the console and the extension rollout for the same maintenance window, outside working hours.
- Confirm in Devices that every active browser is Online now and its policy is Up to date. Browsers sync every minute on their own.
- From a checkout of the new release, apply migrations with
bun run db:migrate. - Deploy the new console build. See Deploy the console.
- Roll out the new extension version to managed browsers.
- Refresh open ChatGPT, Claude and Gemini tabs so they load the current content script.
- After the rollout, reset any browser whose extension settings still show a sync error, or that Devices shows as Needs attention on the new version.
Limit. Between deploying the console and the new extension reaching a browser, that browser keeps fetching and enforcing the policy but cannot report: the console rejects its reports and heartbeats with HTTP 426, and Devices keeps showing the old version. Prompts matched in that window stay queued with the old version and are still rejected after the update, so that browser must be reset and its pending reports are lost. Keep the window short.
Migrations
bun run db:migrate applies each migration once and records it in the schema_migrations table. 001-platform.sql creates accounts, organizations, named policies with versions, teams, enrollment, devices and activity, including expiring prompt versions, file names and file findings. 002-app-days.sql adds the AI apps each browser opened per day. 003-app-labels.sql adds each organization’s AI app labels.
A database that applied 009-file-findings.sql before the migrations were combined already has this schema. Reset any older database and bootstrap it again. Policy versions saved before 0.7.0 have no AI app discovery setting and the console can’t read them, so reset a database from an earlier release as well.
Reset a browser
Reset removes the browser’s local enrollment, cached policy and pending reports. Pending reports are lost.
- Open the extension settings and choose Reset this browser.
- Confirm with Reset enrollment. Keep enrollment or Escape cancels.
- Wait for the status to say the browser was reset, then enroll it with a new one-time code.
Security. Reset does not revoke the device in the console. The device stays registered until an administrator chooses Revoke access under Devices, and each new enrollment adds a device that counts toward the 500-browser limit.