Google Meet
Pilot-ready browser-extension coverage for the consenting user's local Meet self-view, with on-device signals and server-controlled escalation.
Local self-view, server authority
A managed Manifest V3 extension discovers the participant's local Meet video as the single-page app replaces elements, then computes bounded liveness and capture-quality signals on the device.
The host page hands over a short-lived credential scoped to one Presence session. The token remains in memory, raw media stays local, and only the Presence server can issue a challenge, escalation, or block directive.
The live probe opens a real Meet URL in a dedicated signed-in Chrome profile, mints a real Presence session from a server-side tenant key, and fails unless the extension finds local video and keeps its sideband connected.
Check it yourself
The artifacts behind this page
- Connector readiness and pilot status./connectors →
- Google Meet's official real-time media boundary.https://developers.google.com/workspace/meet/media-api/guides/overview →
What this page does not claim
Limits
- The first authenticated, in-call probe still needs a disposable Meet URL, a dedicated signed-in Chrome profile, and a Presence pilot tenant key. Until it passes, this remains a reference implementation rather than a generally available connector.
- This path does not inspect remote-participant streams, install a Meet bot, or depend on Google's Developer Preview Meet Media API.