OpenAI opens Codex Computer Use and Chrome extension in the EEA, UK, and Switzerland

• OpenAIDevs said Codex is rolling out four Europe-facing features this week across the EEA, UK, and Switzerland: Computer Use, the Chrome extension, personalized memory, and Chronicle.
• Wes Roth's rollout summary added two practical caveats: memory stays disabled by default in those regions, and Chronicle is still an optional research preview for ChatGPT Pro subscribers on macOS.
• According to Varun Bhat's rollout post, the expansion gives Codex three new surfaces at once in Europe: desktop app control, browser automation, and persistent context across work.
• Kevin Kern's settings walkthrough and TestingCatalog's CDP note surfaced a more technical wrinkle: browser use can be upgraded with full Chrome DevTools Protocol access for deeper web app debugging.

You can jump from OpenAIDevs' announcement to Varun Bhat's rollout post, then straight into Kevin Kern's hidden-browser-setting walkthrough. Derrick K.'s memory note is also more revealing than the launch copy, because it frames Memories and Chronicle as a shift from prompt engineering toward much looser, persistent prompting.

OpenAI's official announcement names the actual geography: EEA countries, the UK, and Switzerland, with the rollout happening this week rather than as a single instant flip.

The feature list is consistent across OpenAIDevs, Varun Bhat, and TestingCatalog's summary:

• Computer Use for desktop apps
• Codex for Chrome for browser automation
• Personalized memory
• Chronicle

The thread replies also clarify one boundary. When asked about India, Varun Bhat's reply said the product had already been available there, which makes this a regional catch-up story rather than a broader global launch.

The biggest practical change is that Europe now gets both desktop control and in-browser task execution, not just one or the other.

Wes Roth's summary describes Computer Use as letting Codex see, click, and type inside desktop apps on macOS and Windows. In the same post, Roth says the Chrome extension can complete tasks across signed-in tabs without taking over the browser.

Several posts point at the same workflow pattern:

• Varun Bhat's examples post suggests form filling, info capture, and issue triage.
• Jerry Liu's Europe post says users can start from an app screenshot and kick off a task.
• pvncher's reaction says Chrome plus Computer Use went from skeptical demo to daily habit.

That pairing matters because the desktop agent and the browser agent can share a task boundary. Varun Bhat pitches it as using apps across a Mac while automating workflows in Chrome, which is a broader workflow than the browser-only agents most people have already seen.

Memory shipped with more caveats than the browser tools.

According to Wes Roth's rollout summary, personalized memory remembers preferences, recurring workflows, tech stacks, and repository conventions when enabled. The same post says memory is disabled by default in these regions.

Chronicle is even narrower at launch. Wes Roth's rollout summary says it builds memories from recent screen activity, but only as an optional research preview for ChatGPT Pro subscribers using macOS.

Derrick K.'s memory note adds the sharpest description of what these two features are for: Codex learns how you work and moves you toward "vague prompting." That is a useful clue about product direction. OpenAI is not only adding more tools in Europe, it is extending the persistence layer that makes those tools less session-bound.

The most technical reveal in the evidence pool is not the regional rollout itself, it is the browser-control mode sitting behind it.

Kevin Kern's walkthrough says a hidden Codex app setting enables full CDP access through Settings, then Browser, then "full CDP access." Derrick K.'s follow-up says that browser mode can then deeply debug web apps through the Chrome DevTools Protocol.

The debugging use cases in Kevin Kern's examples are concrete:

1. Inspect whether a broken login flow is failing on the request, cookie, or redirect.
2. Compare what app code expects after reload with what the browser actually sees.

That gives the Chrome extension a second identity. It is partly an automation surface, but TestingCatalog's note also frames it as a site inspection and modification tool, which pushes Codex closer to a browser-native debugging agent than a simple click bot.