Set Up the Demo Extension

macOS

1. Install Chrome Canary if it is not already on the machine.
2. Download the profile that force-installs the extension: demo.mobileconfig. It already has this extension's id and this server's update URL built in.
3. Double-click the downloaded file. It opens System Settings. Go to General, then Device Management. Find "Agentforce Demo: Force-install WebRTC Diagnostics Relay" and click Install. Enter your password when asked.
4. A plain managed-preferences plist does not work on current macOS. Chrome never receives the value at all, the profile above is what actually reaches it. Some older macOS releases still accept a plain plist drop.
5. Quit Canary completely (Cmd-Q, not just closing the window) and relaunch it from Terminal with the flag that turns the API on.

   "/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary" \
     --enable-features=ApiEnterpriseWebrtc

   The Dock icon does not carry this flag. Launching Canary from the Dock after this step leaves the API off even with the extension installed.
6. Open chrome://extensions, find WebRTC Diagnostics Relay, and click Extension options. Set Ingest base URL to https://sf.patrickkettner.com and Demo token to the value Patrick gives you, then save.
7. Check chrome://policy for ExtensionSettings. "Not set" means the profile was not approved in System Settings. If it is set but the extension never appears force-installed, this Mac is not carrying enough management authority for Chrome to trust an off-store extension policy. A profile installed by hand this way is still local device management, the same low trust tier as a bare plist. A Mac already enrolled in real MDM does not hit this.

Windows

1. Install Chrome Canary.
2. Force-install the extension through Chrome's machine policy. Canary reads policy from the same registry key as every other channel, HKLM\SOFTWARE\Policies\Google\Chrome. There is no separate Canary policy key on Windows.

   reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v ExtensionSettings /t REG_SZ /d "{\"hchndajkciejddfgpilblfimhldechnk\":{\"installation_mode\":\"force_installed\",\"update_url\":\"https://sf.patrickkettner.com/ext/update.xml\"}}"

3. Quit Canary completely and relaunch it with the flag that turns the API on.

   "%LOCALAPPDATA%\Google\Chrome SxS\Application\chrome.exe" --enable-features=ApiEnterpriseWebrtc

   The Start menu and taskbar shortcuts do not carry this flag.
4. Open chrome://extensions, find WebRTC Diagnostics Relay, and click Extension options. Set Ingest base URL to https://sf.patrickkettner.com and Demo token to the value Patrick gives you, then save.
5. A registry policy alone is not enough on an unmanaged machine. Chrome treats an off-store force-installed extension as low-trust and blocks it unless the machine is domain-joined through Active Directory or enrolled in Chrome Browser Cloud Management. This is not a mistake in the steps above, it is Chrome's own policy trust model, and it applies here even though the registry key is set correctly.

Linux

Chrome Canary does not exist on Linux, and this demo targets Canary specifically. chrome.enterprise.webrtc is gated behind a flag that is off by default in every channel right now, with no chrome://flags entry, so the flag has to be passed on the command line no matter which channel runs it.

When Chrome turns that flag on by default, it lands the same way every Chrome feature does, through Dev, then Beta, then Stable, after Canary. A Linux user without Canary gets the API once it reaches a channel already installed there, not before this demo works on Linux.