Codex for Chrome: Browser Extension Brings Codex to Your Signed-In Web Apps
CodexOpenAI launched a Chrome extension that enables Codex to operate directly within the browser, handling tasks that require access to signed-in web applications like LinkedIn, Salesforce, Gmail, and internal tools. Unlike the Codex desktop app's built-in browser, the Chrome extension uses the user's existing Chrome session — meaning Codex can act on authenticated pages without the user needing to log in again. Codex works in task-specific Chrome tab groups, operating in the background without interrupting the user's active browsing session. Users retain full control over which websites Codex can access, with per-host approval prompts and configurable allowlists and blocklists.
Sources & Mentions
5 external resources covering this update
A New Browser Footprint for Codex
On May 7, 2026, OpenAI introduced the Codex Chrome extension, a new integration that extends the Codex AI coding and task automation platform into Google Chrome. The extension marks a meaningful expansion of Codex's reach: rather than requiring users to spin up a separate browser environment, Codex can now operate within the Chrome browser session users already have open — complete with their existing authentication state and signed-in accounts.
According to OpenAI, the motivation for the Chrome extension came directly from usage patterns observed after the launch of Computer Use in the desktop Codex app. Most common workflows that Codex's computer use capability was being used for happened in the browser. The Chrome extension is designed to make those browser-based workflows faster and more seamless by leveraging the user's real Chrome session rather than an isolated browser environment.
What Codex Can Do in Chrome
With the extension installed, Codex can be directed to perform a wide range of browser-based tasks:
- Research and data gathering — reading and summarizing pages across multiple tabs simultaneously
- CRM and SaaS updates — updating records in Salesforce, reviewing dashboards, navigating internal tools
- Multi-step form workflows — filling and submitting forms across logged-in applications
- Web app debugging — using Chrome DevTools to inspect browser behavior and debug web application flows
Codex operates within task-specific Chrome tab groups, which means browser work tied to a particular Codex thread stays organized and separate from the user's regular browsing. Codex does not take over the active browser session — it works in the background, in parallel with the user's normal activity.
The extension is invoked naturally within Codex threads using @Chrome mentions, for example: @Chrome open Salesforce and update the account from these call notes.
Installation and Access Controls
The Chrome extension is installed through the Codex Plugins menu, following a guided setup flow. Once installed, the extension shows a "Connected" status in the Chrome toolbar to confirm the link between the Codex desktop app and the browser.
OpenAI built granular access controls into the extension. By default, Codex requests confirmation before interacting with any new website, using the host domain (e.g., example.com) as the basis for the decision. When prompted, users can:
- Allow access for the current chat only
- Always allow the host for future use
- Decline access entirely
Persistent allowlists and blocklists can be managed through the Computer Use settings panel. Two elevated-risk options — "Always allow browser content" (which disables confirmation prompts) and "Browser history" access — are available but flagged explicitly as higher-risk choices.
Privacy and Data Handling
The extension requests browser permissions including page debugger access, website data modification rights, browsing history access, and notification capability. OpenAI states that only browser activity that becomes part of Codex's active context — page text, screenshots, tool calls, and thread messages — is stored. Complete separate browsing records are not retained.
When Codex's Memories feature is enabled, relevant saved memories can assist with Chrome-based tasks, allowing Codex to carry context about user preferences and account details across sessions.
Platform and Limitations
The Chrome extension works on both macOS and Windows. At launch, OpenAI does not support other Chromium-based browsers. For development workflows involving localhost, file-backed previews, or public pages that don't require authentication, OpenAI recommends using Codex's built-in in-app browser instead of the Chrome extension.
OpenAI reports that Codex now has more than 4 million weekly active users — an 8x increase since the start of 2026 — highlighting the rapid adoption of the platform as it expands beyond developer tooling into broader productivity workflows.