OpenAI has shipped a Chrome extension that allows its Codex agent to read and act inside a user’s real, signed‑in Chrome session on macOS and Windows. The extension enables the agent to work across authenticated sites and internal tools — examples specifically cited include LinkedIn, Salesforce and Gmail — and is not available in the EU and UK during this rollout. This change matters because it gives Codex direct access to account contexts that were previously unavailable to its sandboxed browser.
Codex now selects among three tool tiers automatically: dedicated plugins for direct integrations, Chrome when a logged‑in browser context is required, and the in‑app sandboxed browser for localhost and public pages that do not require sign‑in. OpenAI lists dedicated plugins such as GitHub, Slack, Figma and Notion; users can also invoke the browser explicitly with an @Chrome mention, and Codex can open Chrome if it is not already running.
The extension builds on OpenAI’s earlier Computer Use feature and responds to a preference for working in a full browser environment. Tasks that were awkward or impossible via APIs or isolated plugins — for example, multi‑step updates across CRM systems or collecting context from several authenticated tabs-are now feasible inside Codex using a real browser profile.
For developers and product teams, the extension adds practical capabilities: Codex can test web apps in a signed‑in state, gather context from multiple open tabs or tab groups, and operate Chrome DevTools in parallel while users continue other work. Task‑specific tab groups keep the agent’s activity isolated so it can perform scripted updates and cross‑site automation without hijacking the active browsing session.
Connecting the extension follows a five‑step flow: install the extension from the Chrome Web Store; add the Chrome plugin inside the Codex desktop app; approve the requested Chrome permissions; confirm the extension shows “Connected” in Chrome’s toolbar; then start a new Codex thread and invoke Chrome. The extension requests permissions that include access to the page debugger; read and change all data on all websites; read and change browsing history on all signed‑in devices; view and manage tab groups; and manage downloads.
OpenAI emphasizes operational limits and user controls. For local development servers, file‑backed previews and public pages that do not require sign‑in, Codex continues to use its in‑app browser so previews and verification remain inside the app. By default Codex prompts before interacting with each new host and offers three response options; users can maintain a permanent allowlist and blocklist via Computer Use. The extension currently supports Chrome only and explicitly excludes other Chromium‑based browsers such as Brave, Edge and Arc.
Sources
Replies (0)
No replies in this topic yet.
