Codex 'Chronicle' Memory
- OpenAI added “Chronicle” to Codex, a memory feature that captures recent project context and screen content for coding workflows. - On Mac, Chronicle processes screenshots in the cloud and stores extracted text memories locally without encryption, and it is unavailable in the EU. - That moves context retention from prompt craft into platform governance questions like consent, observability, retention policy, and tenant isolation. (thenextweb.com)
OpenAI has added Chronicle to Codex, an opt-in memory feature that uses recent screen context to help the coding agent remember what you were doing. (developers.openai.com) Chronicle is in research preview on macOS for ChatGPT Pro subscribers, and OpenAI says it is not yet available in the European Union, the United Kingdom, or Switzerland. It requires macOS Screen Recording and Accessibility permissions to run. (developers.openai.com) The feature sits on top of Codex’s broader memory system, which is off by default and stores summaries, durable entries, recent inputs, and supporting evidence under the user’s local `~/.codex/memories/` directory. OpenAI says users can inspect those files and control memory behavior per thread with the `/memories` command. (developers.openai.com) OpenAI describes Chronicle as a way for Codex to infer missing context from what is on screen, such as a failed GitHub Actions run, a draft document, or a teammate’s name in Slack, instead of making the user restate that context in a prompt. The company says Codex can also learn recurring tools and workflows over time. (developers.openai.com) That changes what “memory” means in a coding assistant. Earlier Codex updates focused on longer threads, scheduled follow-up work, and preserving context inside the app; Chronicle adds context from the desktop itself. (openai.com) OpenAI’s own documentation flags three risks before users turn Chronicle on: it can consume rate limits quickly, it increases exposure to prompt injection, and it stores memories unencrypted on the device. Those warnings put privacy and security controls at the center of the feature, not at the margins. (developers.openai.com) Reporting from The Next Web said the macOS version sends screenshots to OpenAI’s servers for processing, then stores the extracted text as local memories without encryption. OpenAI’s Chronicle page says only that the feature “augments Codex memories with context from your screen,” without describing that pipeline on the main page. (thenextweb.com, developers.openai.com) The timing fits a broader April 16, 2026 push to turn Codex from a code generator into a desktop agent that can see, click, type, browse, review pull requests, connect over Secure Shell, and use more than 90 plugins. Chronicle extends that same pitch from action to recall. (openai.com, community.openai.com) For developers, the immediate tradeoff is convenience against control: less repeated setup in each session, in exchange for screen access, local memory files, and a new surface for data handling rules. Chronicle starts as a coding feature, but it lands as a policy feature too. (developers.openai.com, developers.openai.com, thenextweb.com)
