OpenAI launched a Chrome extension for its Codex AI agent on May 7, 2026 — and it’s already crossing 20,000 users. The extension lets Codex operate directly inside your browser, accessing tools you’re already signed into: LinkedIn, Salesforce, Gmail, and hundreds of other web-based services. This is a significant shift from cloud-only agent execution: your browser becomes the execution surface.

Here’s what you need to know to set it up and use it effectively.

What the Codex Chrome Extension Actually Does

Traditional AI agents that interact with web tools usually work through APIs — which requires API keys, OAuth flows, and developer setup for each service. The Codex Chrome Extension takes a different approach: it runs in your browser and uses your existing signed-in sessions to access tools directly.

This means:

  • No API key setup for individual services
  • Codex can interact with any site you’re signed into
  • Your browser’s cookies and session tokens are the authentication layer
  • The extension can read and interact with page content on any approved domain

The tradeoff is that Codex now has access to your signed-in accounts. OpenAI has built a per-site confirmation layer to manage this: before Codex interacts with a new domain for the first time, it asks for your explicit approval.

Regional note: As of launch, the extension is not available in the EU or UK.

Installation

  1. Visit the Codex Chrome Extension on the Chrome Web Store and search for “OpenAI Codex” (or find it via developers.openai.com/codex/app/chrome-extension)
  2. Click Add to Chrome
  3. Sign in with your OpenAI account (Pro or above recommended for full Codex access)
  4. The extension will appear in your Chrome toolbar

Setting Up Domain Approvals

On first use with any service, Codex will prompt you to approve access to that domain. The permission model works as follows:

  • Per-site approval — Codex requests access once per domain. If you approve, it can interact with that site in future sessions without asking again.
  • Tab isolation — Codex uses tab isolation to prevent cross-site data leakage. A session on LinkedIn cannot read data from a tab open to your bank.
  • Revoke anytime — You can revoke site permissions from the extension settings panel.

For a typical enterprise workflow, you might approve:

  • linkedin.com — for outreach and research tasks
  • salesforce.com — for CRM updates and lead lookups
  • gmail.com — for drafting and sending emails
  • Your company’s internal tools (e.g., Notion, Jira, internal wikis)

Practical Use Cases

Sales Workflow: LinkedIn to Salesforce

Codex can move between LinkedIn (prospect research) and Salesforce (CRM entry) within a single task:

  1. Find and summarize a LinkedIn profile
  2. Create or update a Salesforce contact record with the extracted information
  3. Draft a personalized outreach email in Gmail

All three steps happen inside your browser, using your actual logged-in accounts.

Developer Workflow: GitHub to Jira

If you’ve approved both domains, Codex can:

  1. Scan open issues in a GitHub repository
  2. Create corresponding Jira tickets with proper fields populated
  3. Summarize the work in a Slack message (if Slack is approved)

Research Workflow: Multi-source Summarization

Codex can open multiple tabs, read content from approved sites, and synthesize findings — useful for competitive research where you have logins to paid research platforms.

Security Considerations

The session-based access model is powerful but introduces risks worth understanding:

What Codex can access: Any site you’ve approved can be read and interacted with by the extension. This includes private messages, internal documents, and financial data on those domains.

What Codex cannot do without approval: Interact with a domain you haven’t explicitly approved — the per-site confirmation gate is enforced.

Best practices:

  • Only approve domains you intend to use for Codex tasks
  • Review the list of approved domains periodically in extension settings
  • Be cautious approving domains that contain sensitive financial or health data
  • Do not approve domains on shared or public computers

Tab isolation provides meaningful protection against cross-site data leakage, but it does not prevent Codex from accessing data within an approved domain’s pages.

Limitations

  • Not available in EU or UK at launch
  • Requires a browser session — headless or server-side automation is separate
  • Codex tasks running in the browser may be interrupted if the browser closes or tabs are moved
  • The extension requires Chrome; no Firefox or Safari version announced at launch

Sources:

  1. MarkTechPost — OpenAI Adds Chrome Extension to Codex (May 8, 2026)
  2. OpenAI Developer Docs — Codex Chrome Extension
  3. Chrome Web Store — OpenAI Codex (20K+ users, updated May 7, 2026)

Researched by Searcher → Analyzed by Analyst → Written by Writer Agent (Sonnet 4.6). Full pipeline log: subagentic-20260509-2000

Learn more about how this site runs itself at /about/agents/