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

Quick Start Guide

Installing and Using the Codex Chrome Extension

Five steps to connect Codex to your signed-in browser. Works on macOS and Windows. Not available in EU or UK yet.

1

Install the extension from the Chrome Web Store

Open Chrome and go to the Codex listing in the Chrome Web Store. Click Add to Desktop and confirm the prompt that appears.

Shows the Codex extension card with version, publisher, and Add to Desktop button

</>
Codex
by OpenAI · v1.1.4 · 109 KiB · Tools
Control Chrome with Codex

Add to Desktop

Codex does not support other Chromium-based browsers (Brave, Edge, Arc) at this time.

2

Add the Chrome plugin inside the Codex app

Open the Codex desktop app and navigate to Plugins. Find the Chrome plugin and click Add. Codex will walk you through the connection flow.

Codex App
›
Plugins
›
Chrome
›
Add

Chrome

Let Codex use your signed-in browser

Add

3

Approve Chrome permissions and confirm “Connected”

Chrome will ask you to accept a set of extension permissions. After approving, open Chrome and confirm the Codex extension shows Connected in the toolbar.

Permissions requested by the extension

Access the page debugger

Read and change all your data on all websites

Read and change your browsing history on all signed-in devices

View and manage your tab groups

Manage your downloads

---

Extension status in Chrome toolbar

Connected

These permissions let the extension operate browser workflows. Codex still applies its own per-site confirmation prompts and allowlist/blocklist on top of these Chrome permissions.

4

Start a new Codex thread and invoke Chrome

Open a new thread in Codex. You can let Codex choose the right tool automatically, or invoke Chrome directly using the @Chrome mention. Codex will open Chrome if it isn’t already running.

@Chrome open Salesforce and update the account from these call notes.

You can also just describe the task naturally — Codex will select Chrome automatically when the task requires a signed-in website.

5

Review and approve site access when prompted

By default, Codex asks before interacting with each new website host. Choose one of three options each time it asks. Manage a permanent allowlist and blocklist in Computer Use settings.

Codex is asking to use salesforce.com

Allow this chat

Always allow host

Decline

Example: Codex working in Chrome

Codex · New thread

@Chrome Go to my LinkedIn notifications, summarize any messages from recruiters, and draft a short reply to each.

Opening Chrome · Requesting access to linkedin.com

Working in tab group · Your active tabs are unaffected

Found 3 recruiter messages in your LinkedIn inbox. Here’s a summary and a draft reply for each:

Sara H. — Eng Manager role
Draft ready

James K. — ML Lead, Series B
Draft ready

Priya M. — Staff Engineer
Draft ready

Task complete · Pages kept open for review

Codex tab group in Chrome

LinkedIn — Inbox

Message · Sara H.

+2 more

Before you use it — three things to know

Treat page content as untrusted. Malicious pages can embed instructions designed to redirect Codex’s behavior (prompt injection). Review websites before approving access.

Memories setting affects browser tasks. If Memories is on, Codex can use previously stored context during Chrome tasks. Turn Memories off for fully isolated sessions.

File uploads need an extra setting. Go to Chrome Extensions › Codex › Details and enable Allow access to file URLs if any task requires uploading a local file.

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.