Codex just got a Chrome extension. Your AI agent can now operate inside your actual browser — updating a logged-in Salesforce account, triaging Gmail, reading LinkedIn profiles. It launched May 7, 2026, and Codex already has over 4 million weekly active users, up 8× from the start of the year.
What does "AI agent inside my Chrome" actually mean?
Codex already had an in-app browser for public pages and localhost. The problem? Most real work happens behind a login. Salesforce CRM, internal BI dashboards, Gmail, Notion — none of those are reachable from a stateless in-app browser.
The Chrome extension fixes that. Codex operates directly inside your signed-in Chrome profile, using your existing cookies and session state. From Codex's perspective, it's like looking over your shoulder at the tabs you already have open.
How is this different from the in-app browser?
Here's a side-by-side.
| Feature | In-app browser | Chrome extension |
|---|---|---|
| Login session | None (public pages only) | Your Chrome profile, as-is |
| Accessible sites | Public URLs, localhost | LinkedIn, Salesforce, Gmail, internal tools |
| Tab management | Single in-app window | Background multi-tab, parallel |
| DevTools access | No | Yes (debugging, DOM manipulation) |
| File uploads | No | Yes, with one setting change |
| Primary use | Local dev server testing | Real SaaS workflow automation |
Codex switches between both as needed — prototype verification in the in-app browser, then escalating to Chrome when authenticated context is required.
What can you actually get it to do?
Three representative scenarios.
Business SaaS automation — Keep your call notes open and tell Codex "@Chrome open Salesforce and update the account from these call notes." Codex opens Salesforce in the background and makes the updates. The same pattern works for support ticket triage, Google Workspace cleanup, and BI dashboard summaries.
Developer testing — With DevTools access, Codex can reproduce bugs in authenticated SPAs, monitor console errors, manipulate the DOM, and validate checkout flows — all via natural language commands in your real production-like environment.
Multi-tab research — Open multiple competitors simultaneously, compare pricing and features across tabs, and get a structured summary delivered — while your own tabs stay untouched.
How to install and use it
- Open the Codex app
Navigate to Plugins. - Add the Chrome plugin
Find "Chrome" in the plugin list and click Add. The guided setup flow starts automatically. - Install the Chrome extension
Follow the prompts to install from the Chrome Web Store and approve Chrome's permission dialog. - Confirm Connected status
The Codex icon in your Chrome toolbar should show "Connected." - Invoke via @Chrome in a new thread
Use "@Chrome open [site] and [task]." First access to a site prompts for permission — choose "Always allow" for recurring sites. - (Optional) Enable file uploads
In Chrome's extension management, turn on "Allow access to file URLs" if tasks involve uploading local files.
Go deeper
OpenAI Codex Chrome extension official docs Step-by-step setup, allowlist/blocklist management, and security settings. developers.openai.com
Codex for Chrome: Capabilities, Architecture, and Use Cases Deep technical coverage of the launch timeline, multi-tab architecture, DevTools integration, and enterprise scenarios. eigent.ai
OpenAI official YouTube demo 2m 35s video showing Chrome-direct use scenarios. youtube.com
MarkTechPost coverage News summary focused on LinkedIn, Salesforce, and Gmail access scenarios. marktechpost.com
