Effective July 26, 2026.

Ossi Browser Bridge for Firefox connects Firefox to a locally running Firefox Codex plugin only when the user explicitly asks Codex to work in Firefox. The extension publisher does not operate an intermediary server and does not receive browsing data.


For an explicitly requested Firefox task, the extension may transmit the selected tab URL and title, visible website content, interactive element descriptions, visible-tab screenshots, and results of requested clicks, typing, scrolling, and navigation.


Data travels directly to locally running Firefox Codex MCP servers through authenticated WebSockets bound to 127.0.0.1:32179–32186. Each active Codex task uses one port. Content included in a Codex task may be processed by OpenAI under the user's account or workspace settings.

The extension does not connect to a publisher-operated server. It does not sell data, display advertising, or run analytics or telemetry.


Initial setup uses a short-lived one-time code. Firefox and Codex each store the same random connection token in local application data. Later connections prove possession through fresh mutual HMAC challenges, so the token is not resent. The token does not contain page content.


Website access is deny-by-default and limited to exact public HTTP(S) origins approved for the current Codex task. Page data is transmitted only for explicitly requested actions.

The extension and MCP bridge do not persist page content, screenshots, origin grants, analytics, telemetry, cookies, or browsing history. Existing Firefox tabs and windows remain user-owned. Users can disable or remove the extension in Firefox and can explicitly reset the local pairing credential from Codex.


Password input fields are technically blocked. The Codex workflow also forbids entering passwords, one-time passwords, recovery codes, payment data, and other secrets.

The integration does not export cookies or history, inspect Firefox profiles or saved passwords, bypass browser security prompts, or run invisible background automation.


Questions, privacy requests, and security reports can be opened through GitHub Issues. Do not include private page content, credentials, or other secrets in an issue.