Codex brings Computer Use, Chrome, Memories and Chronicle to Europe
OpenAI's June 16 Codex changelog says more Codex app capabilities are now rolling out in the EEA, the UK, and Switzerland, including Computer Use, the Chrome extension, Memories, and Chronicle.
OpenAI's June 16, 2026 Codex changelog matters because it turns several previously limited Codex app capabilities into a practical option for users in the European Economic Area, the United Kingdom, and Switzerland. The update covers four surfaces: Computer Use, the Codex Chrome extension, Memories, and Chronicle. For European developers, the practical question is now less "can I use these Codex app features at all?" and more "which one should I trust for this workflow?"
Key takeaways
- Computer Use is now available for Codex app users on macOS and Windows in the EEA, UK, and Switzerland.
- The Codex Chrome extension is available for browser tasks that need signed-in Chrome context and can work across tabs in the background.
- Memories can carry useful preferences, recurring workflows, tech stacks, and repository conventions into future Codex work, but they are off by default in these regions.
- Chronicle is available as an opt-in research preview for ChatGPT Pro subscribers on macOS, using recent screen context to help build Codex memories.
- The rollout is powerful, but the safest setup is still feature-specific: use browser tools for browser work, Computer Use for GUI-only desktop work, and Memories or Chronicle only when the stored context is worth the privacy tradeoff.
Why it matters
This is a regional availability update, but it changes the day-to-day shape of Codex in Europe. Computer Use gives Codex a path into desktop workflows where files, terminal output, or APIs are not enough. That includes native app testing, GUI-only bugs, app settings, and workflows that span more than one local app.
The Chrome extension is a different tool. It is designed for browser tasks that need the user's signed-in Chrome state, such as admin dashboards, internal tools, or SaaS products where a clean public preview is not enough. OpenAI's docs also keep the important boundary clear: for localhost previews and public pages that do not require sign-in, the in-app browser should usually come first.
Memories and Chronicle are the bigger context shift. Memories can reduce repeated setup by remembering durable preferences and repo conventions. Chronicle goes further by using recent screen context to help build those memories, but it is still opt-in, macOS-only, and limited to ChatGPT Pro subscribers during the research preview.
| Capability | Best use | Main caveat | Source |
|---|---|---|---|
| Computer Use | Desktop apps, GUI testing, settings, visual bug reproduction | Can affect app and system state outside the project workspace | OpenAI Computer Use docs |
| Codex Chrome extension | Signed-in browser workflows across tabs | Browser pages and signed-in actions need careful review | OpenAI Chrome extension docs |
| Memories | Stable preferences, repo conventions, recurring workflows | Off by default in the EEA, UK, and Switzerland | OpenAI Memories docs |
| Chronicle | Building memories from recent screen context | Opt-in research preview for ChatGPT Pro on macOS | OpenAI Chronicle docs |
For a broader map of where these features fit into everyday agent work, LinkLoot's /guides/ai-agent-tools is the right follow-up.
What to try first
Start with the least invasive tool that can complete the job. If the task is a local web preview, use the in-app browser first. If the task needs an authenticated browser session, use the Chrome extension and approve only the relevant website. If the task depends on a desktop interface, use Computer Use with a narrow target app and review permission prompts before continuing.
For Memories, treat the feature like a local recall layer, not a replacement for project documentation. Keep durable team rules in AGENTS.md, READMEs, or repo docs. Let memories help with preferences and repeated workflows, but do not rely on them as the only place where important instructions live.
Chronicle needs the most deliberate opt-in. It can make Codex feel less context-starved, but screen-derived context is sensitive by nature. Before enabling it, review what apps are visible, what secrets could appear on screen, and whether the productivity gain is worth the extra context surface.
Source check
The primary OpenAI Codex changelog confirms the June 16 regional rollout for the EEA, UK, and Switzerland and names the four affected capabilities: Computer Use, the Chrome extension, Memories, and Chronicle.
The supporting OpenAI docs confirm what each capability is for. Computer Use is documented as a way for Codex to see and operate graphical interfaces on macOS or Windows. The Chrome extension docs position it for signed-in browser tasks. The Memories docs confirm that memories are off by default in the EEA, UK, and Switzerland, and the Chronicle docs confirm the opt-in research preview scope for ChatGPT Pro subscribers on macOS.
OpenAI says more Codex app capabilities are rolling out to users in the EEA, the UK, and Switzerland: Computer Use, the Codex Chrome extension, Memories, and Chronicle.
The useful takeaway: Codex in Europe now has more of the app-level surface area that made the product interesting elsewhere, but the best workflow is still selective. Use each capability only where it solves a real bottleneck, and keep permissions, stored context, and signed-in browser access under active review.