Relay Protocol

When auto-pair is enabled:

1. The extension calls the local discovery endpoint (/config) to learn the relay port and pairing requirement.
2. If pairing is required, it fetches the token from /pair.
3. The extension connects to the relay with the pairing token.

/config and /pair reject explicit non-extension origins. Chrome extension requests may omit the Origin header, so the relay also accepts missing-Origin requests. CLI/tools may call /config and /pair to auto-fetch relay settings and tokens.

Relay ops endpoint: ws://127.0.0.1:<relayPort>/ops. The CLI/tool connect command accepts base relay WS URLs

(for example ws://127.0.0.1:<relayPort>) and normalizes them to /ops.

Legacy relay /cdp is still available but must be explicitly opted in (CLI: --extension-legacy).

When pairing is enabled, both /ops and /cdp require a relay token (?token=<relayToken>). Tools and the CLI auto-fetch /config and /pair

to obtain the token before connecting, so users should not manually pass or share tokenized URLs.

Readiness checks:

npx opendevbrowser status --daemon --output-format json

npx opendevbrowser --help

node scripts/chrome-store-compliance-check.mjs

Expected extension-ready daemon fields:

• extensionConnected=true
• extensionHandshakeComplete=true