OPEN LINK ↗
// 2h agoPRODUCT UPDATE
Codex lands signed-in Chrome browser control
OpenAI has added a Chrome extension for Codex that lets the agent operate inside a real signed-in browser session, which makes authenticated workflows like Gmail, Salesforce, LinkedIn, and internal admin tools practical instead of fragile. The update also introduces host-based approval flows, allowlist and blocklist controls, and additional browser-safety guardrails so teams can decide when Codex may touch a site and when it must ask first.
// ANALYSIS
This is a meaningful product maturity step: Codex is moving from sandboxed web work toward the messy, high-value browser workflows where identity, session state, and permissions actually matter.
- –The main unlock is signed-in browser context, which is what most enterprise tools require.
- –Host-level approvals are the right abstraction here because they are easier to reason about than page-by-page prompts.
- –The allowlist/blocklist model makes the feature more deployable for teams that need governance, not just convenience.
- –The security posture is still cautious, which is good; browser tasks are inherently high-risk and page content should be treated as untrusted.
// TAGS
codexopenaibrowser-extensionweb-agentagentautomationsecurity
DISCOVERED
2h ago
2026-05-10
PUBLISHED
2h ago
2026-05-10
RELEVANCE
9/ 10
AUTHOR
AICodeKing