OpenAI Adds Chrome Extension to Codex, Letting Its AI Agent Access LinkedIn, Salesforce, Gmail, and Internal Tools via Signed-In Sessions

OpenAI has launched a Codex Chrome extension for Mac and PC to streamline browser-based workflows that were previously difficult to handle via APIs or plugins. This release follows a trend where most users preferred working in a browser after the launch of “Computer Use,” allowing Codex to operate more effectively across various web-based tasks.

What the Extension Actually Does

Before 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. The new Chrome extension fills a gap those two approaches couldn’t cover: tasks that require your real, signed-in browser state.

The Codex Chrome extension lets Codex use Chrome for browser tasks that need your signed-in browser state. It is intended for use when Codex needs to read or act on sites such as LinkedIn, Salesforce, Gmail, or internal tools. For everything else like local development servers, file-backed previews, and public pages that do not require a sign-in you can continue using the in-app browser, which keeps that preview and verification work inside Codex without touching your Chrome profile.

Codex now operates across three distinct tool tiers depending on the task: plugins when a dedicated integration is available, Chrome when it needs logged-in browser context, and the in-app browser for localhost. The agent selects which tier to use automatically, though users can also invoke Chrome directly in a prompt using the @Chrome mention 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 new browser-based capabilities of the plugin include testing web apps, collecting context from across open tabs, and using Chrome DevTools in parallel while the user performs other tasks. Critically, Codex works in task-specific tab groups, so it can gather context and take actions without taking over your active browsing session.

How to Install and Use Codex Chrome extension

Permission Model and Security Considerations

The Codex Chrome extension requires extensive browser permissions—including access to your history, bookmarks, and page data—to function as an integrated AI agent. To mitigate security risks, OpenAI has implemented a per-site confirmation layer that asks for permission before Codex interacts with a new domain. Users can manage these permissions via an allowlist or blocklist, though certain features like browser history access carry higher risk and require manual approval for each session.

Beyond standard permissions, developers must be wary of prompt injection, where malicious website content could potentially take over Codex’s instructions. To ensure data privacy, OpenAI only stores browser activity when it is explicitly added to a chat’s context, such as through screenshots or text summaries. For those seeking maximum isolation, turning off the Memories feature ensures that browser-based tasks remain untainted by previous session data or user preferences.

Check out the Chrome Extension, and Full Docs. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us

The post OpenAI Adds Chrome Extension to Codex, Letting Its AI Agent Access LinkedIn, Salesforce, Gmail, and Internal Tools via Signed-In Sessions appeared first on MarkTechPost.