ChatGPT for Mac adds opt-in Computer History feature, replacing Chronicle

What happened

I have the source facts and the structure you specified. I’ll draft 6–8 analytical paragraphs from those details only—no invented versions, dates, or figures, and no markdown.OpenAI is adding an opt-in Computer History feature to ChatGPT for Mac, and it replaces Chronicle. The change is not limited to the chat window. OpenAI is giving both ChatGPT and Codex a way to learn from and remember how you use your Mac, including work that happens outside the ChatGPT app. That pairing matters as much as the rename. ChatGPT is the general assistant surface. Codex is the coding surface. Computer History is the shared memory layer that can sit under both. 9to5Mac reports the feature as opt-in, which means the product is not claiming silent capture of a Mac as a default. The user has to turn it on. The replacement of Chronicle is also a product statement. Chronicle was the prior name and path for this kind of Mac-side memory. Computer History is the successor, not a second, parallel log sitting next to the old one.

The mechanics implied by the names are more important than the branding. Computer History has to persist something about how the Mac is used, then make that history available later so ChatGPT and Codex can learn from it and remember it. The hard part is the outside-the-app clause. If the only context were typed into ChatGPT, there would be nothing new to ship. Work outside the app is the actual scope: other applications, other windows, other sessions, other files, other terminals, other browsers. The Mac client is the observation point. ChatGPT and Codex are the consumers. Opt-in is the gate. Replacing Chronicle means the capture path, the storage path, or the retrieval path that used to live under that name is being retired rather than left as a second history store. The architecture, if it is going to do what the summary says, has three stages. First, the Mac app is allowed to notice activity beyond its own UI after the user opts in. Second, that activity is turned into a history the models can learn from, not just a transcript of the last chat. Third, both ChatGPT and Codex can recall that history when the next task starts, including a task that never mentioned the earlier work inside the app. None of that requires a version number to be useful. It does require a clear split between local observation, stored history, and model-facing memory.

The technical detail

For engineers and builders, the Codex side is the part that changes daily work. A coding agent that only knows what you pasted into it is a chat box with extra steps. A coding agent that can remember how you use the Mac, including the work that never entered the ChatGPT window, is closer to a teammate that has been sitting at the same desk. That is the difference between explaining a repo again and having the agent already know which apps, which files, and which habits showed up while you were building. ChatGPT getting the same history is the other half. Debugging a production issue, writing a design note, and then asking ChatGPT for a summary should not require re-teaching the machine what you just did in a browser, an editor, or a local tool. Builders who already treat ChatGPT as a second brain and Codex as a pair programmer now have a reason to keep both on the same Mac instead of splitting context across machines or across paste buffers. The opt-in flag is also an engineering decision. A team that wants this memory can turn it on. A team that cannot send Mac activity into an assistant can leave it off. That is a cleaner contract than a feature that only works if the user remembers not to open the wrong window.

Why it matters for builders

The market context is the race to make assistants useful between prompts, not only during them. A Mac-only, opt-in history that feeds ChatGPT and Codex is OpenAI arguing that the desktop, not the tab, is the right place to collect that memory. Other assistants already try to see more than the text box: computer-use agents, screenshot-style recall, on-device OS summaries, IDE plugins that index the current repo. Computer History is OpenAI’s version of that claim, attached to the ChatGPT for Mac client and aimed at both chat and code. Replacing Chronicle is how you know this is not a side experiment. Chronicle was the earlier attempt to give the Mac client a memory of the machine. Computer History is the productized name and the replacement. Competitors that only remember the current thread, or that only see the current IDE buffer, are now being compared against a client that says it can remember Mac use even when that use never entered the app. The constraint is the platform. This is ChatGPT for Mac. Windows, Linux, and browser-only users do not get this path from this change. That keeps the feature sharp and also keeps it narrow. OpenAI is betting that Mac users who already run ChatGPT and Codex on the same machine are the people who will notice the missing context first.

Market and competitive context

The practical takeaway is to treat Computer History as a permission and a data flow, not as a nicer chat log. If you turn it on, assume ChatGPT and Codex can later act as if they watched the Mac, not only as if they read the last thread. Decide, before you opt in, which work on that machine is allowed to become assistant memory. Separate personal Macs from work Macs if the two cannot share a history. If you use Codex, test whether a task that started outside the app is actually easier on the next turn, or whether the history is too coarse to matter. If you used Chronicle, do not assume the old controls, the old retention, or the old name still apply. Computer History replaces it. Watch three things next. Watch what the opt-in screen actually grants, because the summary only says the feature is opt-in, not what surfaces, apps, or time window it covers. Watch whether ChatGPT and Codex share one history or keep two views of the same Mac. Watch whether OpenAI keeps this Mac-only or treats the ChatGPT for Mac client as the first ship of a broader computer-history idea.

What to watch next

The open risks sit in the same place as the value. A history of how you use a Mac is a history of unsent drafts, private messages, credentials on screen, customer data, and half-finished code. Opt-in reduces surprise. It does not reduce the blast radius after the user says yes. Replacing Chronicle creates a second problem: people who understood the old name may not recognize the new one, and people who never used Chronicle may turn on Computer History without realizing it is the successor to a machine-wide memory feature. There is also an accuracy problem. Learning from and remembering Mac use is not the same as understanding it. If the history is noisy, ChatGPT will sound confident about the wrong window. If the history is incomplete, Codex will remember a fragment and miss the build that happened in another tool. Related prior art is every desktop recorder, every accessibility-based assistant, and every coding agent that already indexes a repo. Computer History is the ChatGPT for Mac version of that idea, pointed at both ChatGPT and Codex, and it only exists if the user opts in. The question left open by 9to5Mac’s report is not whether OpenAI wants the Mac to be a memory source. That is already stated. The question is how much of the machine Computer History is allowed to see once Chronicle is gone, and how much of that seeing ChatGPT and Codex will actually use.