Codex adds Chrome browser control

This turns Codex from a coding agent into a browser-native operator, which is where a lot of real work actually lives.

• –The biggest value is access to authenticated workflows that APIs and localhost-only tools can’t cover
• –Tab-group isolation is a practical detail: it makes long browser tasks easier to manage and less chaotic
• –The explicit approval model is the right tradeoff for an extension with broad website and history permissions
• –OpenAI is clearly positioning Codex to switch modes across plugins, Chrome, and the in-app browser depending on the task
• –This is incremental product work, but it expands Codex’s surface area in a meaningful way for developers and operators