OpenAI Adds Chrome Extension to Codex, Lets Its AI Agent Access LinkedIn, Salesforce, Gmail, and Internal Tools During Login Sessions
OpenAI launched a Codex Chrome extension for Mac and PC to streamline browser-based workflows that were previously difficult to manage with APIs or plugins. This release follows the trend where most users prefer to work in a browser after the introduction of “Computer Usage,” which allows Codex to work more efficiently for all web-based tasks.
What the Extension Actually Does
Prior to this release, Codex had access to an in-app browser — a sandboxed browser built into the Codex desktop app itself — and a growing library of dedicated plugins for services like GitHub, Slack, Figma, and Notion. A new Chrome extension fills a gap that those two methods can’t fill: functions that require your actual browser status to sign in.
The Codex Chrome extension allows Codex to use Chrome for browser functions that require your browser login status. It is intended for use when Codex needs to read or take action on sites such as LinkedIn, Salesforce, Gmail, or internal tools. For everything else like local development servers, file-based previews, and public pages that don’t require a login you can continue using the in-app browser, which keeps those previews and authentication functions within Codex without touching your Chrome profile.
Codex now works across three different tool categories depending on the task: plugins if a dedicated integration is available, Chrome if it requires a login browser context, and an in-app localhost browser. The agent chooses which tier to use automatically, although users can also request Chrome directly on the fly using @Chrome explain the syntax – for example: @Chrome open Salesforce and update the account from these call notes. If Chrome isn’t already open, Codex can open it.
On the performance side, the plugin’s new browser-based capabilities include exploring web apps, collecting content from all open tabs, and running Chrome DevTools concurrently while the user performs other tasks. Importantly, Codex works in task-specific tab groups, to gather context and take action without taking up your active browsing time.
How to install and use Codex Chrome extension
Quick Start Guide
Installing and using the Codex Chrome Extension
Five steps to connect Codex to the browser you’re signed in to. Works on macOS and Windows. Not available in EU or UK yet.
Install the extension from the Chrome Web Store
Open Chrome and go to the Codex list in the Chrome Web Store. Click Add to desktop and confirm the command that appears.
⚠ Codex does not support other Chromium-based browsers (Brave, Edge, Arc) at this time.
Add a Chrome plugin inside the Codex app
Open the Codex desktop app and navigate to Plugins. Find the Chrome plugin and click Add. Codex will guide you through the communication flow.
Codex App
›
Plugins
›
Chrome
›
Add
Chrome
Let Codex use the browser you’re signed in to
Add
Authorize Chrome permissions and make sure it’s “Connected”
Chrome will ask you to accept a set of extension permissions. After authorizing, open Chrome and verify the Codex extension shows It is connected on the toolbar.
Permissions requested by the extension
Extension status in Chrome toolbar
These permissions allow the extension to run the browser’s workflow. Codex still uses its own per-site verification commands and whitelist/blocklist on top of these Chrome permissions.
Start a new Codex thread and invoke Chrome
Open a new thread in the Codex. You can let Codex choose the right tool automatically, or ask Chrome directly using @Chrome say it. Codex will open Chrome if it’s not already running.
@Chrome open Salesforce and update the account from these call notes.
You can also define the task naturally — Codex will automatically choose Chrome when the task requires a signed-in website.
Review and approve site access when prompted
By default, Codex asks before connecting to each new website host. Choose one of the three each time it asks. Manage permanent whitelists and blocklists Computer usage settings.
The Codex begs to be used salesforce.com
Allow this discussion
Always allow the host
Refuse
Example: Codex running on Chrome
@Chrome Go to my LinkedIn notifications, summarize any messages from employers, and write a short reply to each one.
Opens Chrome · Requests access to linkedin.com
Working in a group of tabs · Your active tabs are not affected
Found 3 recruitment messages in your LinkedIn inbox. Here is a summary and response to each draft:
Sara H. – Role of Eng Manager
The draft is fine
James K. — ML Lead, Series B
The draft is fine
Priya M. – Staff Engineer
The draft is fine
Task completed · Pages are kept open for review
Codex tab group in Chrome
LinkedIn – Inbox
Message · Sara H.
+2 more
Before using it – three things you should know
Treat page content as untrusted. Malicious pages can embed instructions designed to redirect Codex behavior (quick injection). Review websites before authorizing access.
Setting memories affects browser functionality. When Memories is enabled, Codex can use previously saved context during Chrome operations. Close Memories in completely separate sessions.
Uploading files requires an additional setting. Go to Chrome Extensions › Codex › Details and enable it Allow access to file URLs if any function needs to load a local file.
Consent Model and Protection Considerations
I Codex Chrome extension it requires broad browser permissions—including access to your history, bookmarks, and page data—to function as an integrated AI agent. To reduce security risks, OpenAI has implemented ia authentication layer for each site asking for permission before Codex can connect to a new domain. Users can manage these permissions through whitelists or blacklists, although certain features such as access to browser history carry significant risks and require manual authorization for each session.
Beyond general permissions, developers must be careful injection immediatelywhere malicious website content may violate Codex directives. To ensure data privacy, OpenAI only stores browser activity when it is explicitly added to the context of the conversation, such as screenshots or text summaries. For those who want a high resolution, turn off the i A feature of memories ensures that browser-based operations remain untainted by previous session data or user preferences.
Check it out Chrome extension, again Complete Documentation. Also, feel free to follow us Twitter and don’t forget to join our 150k+ ML SubReddit and Subscribe to Our newspaper. Wait! are you on telegram? now you can join us on telegram too.
Need to work with us on developing your GitHub Repo OR Hug Face Page OR Product Release OR Webinar etc.? contact us
