OpenAI has launched the Codex Chrome extension for Mac and PC to simplify browser-based workflows that were previously difficult to handle via APIs or plugins. This release follows a trend where most users preferred to work in the browser after the launch of Using Your PC, allowing Codex to work more effectively across various web-based tasks.
What the extension actually does
Prior to this release, Codex had access to an in-app browser – a sandbox browser built into the Codex desktop app itself – and a growing library of custom plugins for services like GitHub, Slack, Figma, and Notion. The new Chrome extension fills a gap that these two methods can’t cover: tasks that require the browser’s actual logged-in state.
The Codex Chrome extension allows Codex to use Chrome for browser tasks that need the state of the browser you’re signed in to. It is intended for use when Codex needs to be read or worked on sites like LinkedIn, Salesforce, Gmail, or internal tools. For everything else like local development servers, file-backed previews, and public pages that don’t require a login, you can continue to use the in-app browser, which keeps the preview and verification working inside Codex without touching your Chrome profile.
Codex now works across three different levels of tools depending on the task: plug-ins when a custom integration is available, Chrome when it needs the context of a logged-in browser, and the in-app browser for localhost. The proxy automatically determines which layer to use, although users can also invoke Chrome directly at the using prompt @Chrome State 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 functional side, the plugin’s new browser-based capabilities include testing web applications, gathering context through open tabs, and using Chrome DevTools in parallel while the user performs other tasks. Most importantly, Codex works in task-specific tab groups, so it can gather context and take action without taking over your active browsing session.
How to install and use Codex Chrome Extension
Quick start guide
Install and use the Codex Chrome extension
Five steps to connect Codex to the browser you are signed in to. Works on Mac and Windows. Not available in the EU or UK yet.
Open Chrome and go to the Codex menu in the Chrome Web Store. Click Add to desktop Confirm the prompt that appears.
⚠ Codex does not support other Chromium-based browsers (Brave, Edge, Arc) at this time.
Open the Codex desktop application and go to Extras. Find the Chrome plugin and click on it He adds. The Codex will guide you through the communication flow.
Codex application
›
Extras
›
chrome
›
He adds
Allow Codex to use the browser you are signed in to
He adds
Chrome will ask you to accept a set of extension permissions. After agreeing, open Chrome and make sure the Codex extension appears connected In the toolbar.
These permissions allow the extension to run browser workflows. Codex still applies its own per-site confirmation prompts and allowed/blocked list on top of these Chrome permissions.
Open a new topic in Codex. You can let Codex choose the appropriate tool automatically, or call Chrome directly using the file
@Chrome Little. Codex will open the Chrome browser if it’s not already running.
@chrome Open Salesforce and update the account from these contact notes.
You can also describe the task normally – Codex Chrome will automatically identify when the task requires a signed-in website.
By default, Codex asks before interacting with each new website host. Choose one of three options each time you are prompted. Manage permanent allowed list and blocked list in Computer usage settings.
Always allow host
decrease
Example: Codex running in Chrome
Open Chrome · Request access to LinkedIn.com
Working in a tab group · Your active tabs will not be affected
3 recruiter messages found in your LinkedIn inbox. Below is a summary and draft response for each:
Sarah H – Engineering Manager role
The draft is ready
james k. – ML Leader, Series B
The draft is ready
Priya M. – Staff engineer
The draft is ready
Task completed · Pages remained open for review
The message: Sarah H.
+2 more
Before using it – three things to know
Treat page content as untrusted. Malicious pages can include instructions designed to redirect script behavior (injection). Review websites before agreeing to access them.
The Memories setting affects browser tasks. If memories are turned on, Codex can use previously stored context during Chrome tasks. Turn off Memories for completely isolated sessions.
File uploads require additional setup. Go to Chrome Extensions › Codex › Details and enable it Allow access to file URLs If any task requires uploading a local file.
Permission model and security considerations
the Codex Chrome Extension It requires extensive browser permissions – including access to history, bookmarks and page data – to act as a full-fledged AI agent. To mitigate security risks, OpenAI has implemented a Confirmation layer for each site Which requests permission before Codex can interact with the new domain. Users can manage these permissions via the allowed list or blocked list, although some features such as accessing browser history come with higher risks and require manual approval for each session.
Beyond standard permissions, developers need to be careful of them Immediate injectionwhere malicious website content is likely to take over Codex instructions. To ensure data privacy, OpenAI stores browser activity only when it is explicitly added to the chat context, such as screenshots or text summaries. For those looking for maximum isolation, turn off Memories feature It ensures that browser-based tasks remain untainted by previous session data or user preferences.
verify chrome extension, and Complete documents. Also, feel free to follow us on twitter Don’t forget to join us 150k+ mil SubReddit And subscribe to Our newsletter. I am waiting! Are you on telegram? Now you can join us on Telegram too.
Do you need to partner with us to promote your GitHub Repo page, face hug page, product release, webinar, etc.? Contact us
