Signed-in browser access
Lets Codex work in Chrome when a task depends on signed-in browser context instead of the in-app browser.
Codex Chrome extension
Codex Chrome extension lets Codex use a signed-in Chrome session for browser tasks that need existing website context, alongside the in-app browser and plugins.
Codex Chrome extension
The Codex Chrome extension lets Codex use Chrome for browser tasks that depend on your signed-in browser state. It is intended for sites where login context matters, such as LinkedIn, Salesforce, Gmail, or internal tools.
For local development servers, file-backed previews, and public pages that do not require sign-in, the page recommends using Codex’s in-app browser first. Codex can switch between plugins, Chrome, and the in-app browser depending on the task, and it asks before using new websites unless you change the access settings.
What the Codex Chrome extension does
Website access controls
Supports interactive approval for each new website, with options to allow once, always allow a host, or decline.
Domain management
Provides allowlists and blocklists in Computer Use settings so teams can manage which domains Codex can revisit or avoid.
Browser history handling
Can use browser history as scoped context when enabled, while warning that history may contain sensitive telemetry, URLs, and activity.
Thread grouping in tab groups
Runs browser tasks in Chrome tab groups so the work for a thread stays grouped together.
Tool switching by task
Works alongside other Codex tools, using plugins where a dedicated integration exists, Chrome for logged-in sites, and the in-app browser for localhost and previews.
Common ways to use it
Work inside authenticated web apps
Have Codex read or act on a signed-in CRM, social, or email session when the work depends on browser state already present in Chrome.
Continue tasks in your existing Chrome session
Use the extension when a task needs browser context from a live Chrome profile rather than a clean localhost or preview environment.
Control access for repeated website workflows
Let Codex handle websites one host at a time with approval prompts, then promote frequently used domains to the allowlist when appropriate.
Bridge gaps between plugins and direct browser work
Switch to Chrome when a task requires a dedicated integration is unavailable and the browser is the best available interface for the job.
Upload local files into browser tasks
Prepare Chrome file access when a browser task needs to upload local files from your machine into a web app.
Pros and Cons
Pros
- Lets Codex work with signed-in websites that the in-app browser cannot access.
- Supports explicit website approval, allowlists, and blocklists for tighter control over browser use.
- Can keep browser work organized in Chrome tab groups for a thread.
- Uses scoped browser history access rather than always-on history access.
Cons
- It depends on Chrome permissions and extension setup, so installation and profile matching matter.
- Browsing history can be sensitive, and the page warns that malicious or misleading content can increase the risk of copying data somewhere unintended.
- If a task requires file uploads, you may need to enable access to file URLs in Chrome.
FAQ
How do you set up the Codex Chrome extension?
The extension is set up from Codex under Plugins. Open Codex, add the Chrome plugin, follow the setup flow, approve Chrome’s permission prompts, and confirm the extension shows Connected in Chrome before starting a new thread.
When should I use Chrome instead of the in-app browser?
Use Chrome when Codex needs your signed-in browser state on sites like LinkedIn, Salesforce, Gmail, or internal tools. For localhost, file-backed previews, and public pages that do not require sign-in, the page recommends using the in-app browser first.
How does website approval work?
By default, Codex asks before it interacts with a new website. You can allow a site for the current chat, always allow a host, decline it, or manage allowlists and blocklists in Computer Use settings.
What permissions does the extension request?
Chrome asks you to accept extension permissions during installation. The permission prompt may include access to the page debugger, browsing history, bookmarks, downloads, tab groups, notifications, and cooperating native applications.
What should I check if Chrome will not connect?
If a Chrome task needs a file upload, the extension must be allowed to access file URLs in Chrome. The setup page also recommends using the same Chrome profile where the extension is installed and re-adding the plugin if the connection fails.
Quick Facts
- Category
- Developer Tool
- Platform
- Chrome extension
- Primary use
- Browser tasks that need signed-in browser state
- Source domain
- developers.openai.com
- Workflow
- Pairs with Codex plugins, Chrome, and the in-app browser
- Setup path
- Codex app > Plugins > Chrome plugin
Codex Chrome extension Alternatives
Timeslicer
Timeslicer is a time tracking and distraction-blocking app that infers tasks from visible browser and desktop content, with activity data stored locally.
DockAMP
DockAMP is a Docker image for browser-based management of Apache or Nginx, PHP, MySQL, MariaDB, PostgreSQL, and proxy containers, plus files, backups, updates, and status tools.
Notwen
Notwen is a freelance finance tool that tracks earnings, tax reserves, and safe spend, with AI for invoicing, contracts, and follow-ups.
ClipStudios
ClipStudios is a web-based AI video platform for creating clips from prompts or images, with built-in audio, lip sync, stitching, and model selection tools. Free tier available; paid plans from €20/month.
drifty
drifty is a Mac AI time tracker that captures app, site, and session context in the background, then classifies activity as focus, neutral, or drift.
Sumora
Sumora is an autonomous outreach agent for LinkedIn and Instagram that finds, qualifies, warms, and books leads, with replies managed in one inbox and final sends under review.