SpyBara
Go Premium

Documentation 2026-08-12 19:59 UTC to 2026-08-13 22:59 UTC

12 files changed +542 −220. View all changes and history on the product overview
2026
Mon 31 19:59 Sat 29 07:02 Fri 28 23:02 Thu 27 21:01 Wed 26 23:58 Tue 25 19:59 Mon 24 22:00 Fri 21 19:59 Thu 20 23:59 Wed 19 22:57 Tue 18 13:01 Mon 17 23:58 Sat 15 01:01 Fri 14 22:00 Thu 13 22:59 Wed 12 19:59 Tue 11 22:59 Mon 10 22:00 Sat 8 03:02 Fri 7 18:59 Thu 6 23:58 Wed 5 19:00 Tue 4 22:00 Mon 3 23:00 Sun 2 21:00
Details

50 icon: "key",50 icon: "key",

51 },51 },

52 {52 {

53 title: "Access tokens",53 title: "Personal Access Tokens",

54 description: "Create and manage tokens for programmatic access.",54 description: "Create and manage tokens for programmatic access.",

55 href: "/codex/enterprise/access-tokens",55 href: "/codex/enterprise/access-tokens",

56 icon: "lock",56 icon: "lock",

57 },57 },

58 {

59 title: "Service accounts",

60 description:

61 "Create and manage workspace identities for automated workflows.",

62 href: "/codex/enterprise/service-accounts",

63 icon: "robot",

64 },

58 ],65 ],

59 },66 },

60 {67 {

Details

450 },450 },

451 },451 },

452 {452 {

453 name: "Chronicle",453 name: "Computer History",

454 href: "/codex/customization/chronicle",454 href: "/codex/customization/computer-history",

455 availability: {455 availability: {

456 bedrock: "unavailable",456 bedrock: "unavailable",

457 },457 },

Details

35 icon: "threads",35 icon: "threads",

36 },36 },

37 {37 {

38 title: "Chronicle",38 title: "Computer History",

39 description:39 description:

40 "Understand how durable memory is collected and managed.",40 "Use recent computer activity as context and manage what is included.",

41 href: "/codex/customization/chronicle",41 href: "/codex/customization/computer-history",

42 icon: "stack",42 icon: "stack",

43 },43 },

44 ],44 ],

Details

1# Computer History

2 

3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

4 

5Computer History is **off by default** for ChatGPT Pro, Business, and

6 Enterprise users in the ChatGPT desktop app on macOS. Pro users can choose to

7 turn it on. For Business and Enterprise workspaces, an administrator must

8 explicitly grant access before each member can choose to turn it on. Computer

9 History also requires [Memories](https://learn.chatgpt.com/docs/customization/memories) and is not

10 available with an API key or Amazon Bedrock. Computer History is not currently

11 available in the European Economic Area (EEA), Switzerland, or the United

12 Kingdom.

13 

14Computer History turns your activity across apps and websites into memories and

15a timeline that ChatGPT and Codex can reference. You can ask natural questions

16about recent work, pick up where you left off, understand patterns in how you

17work, and turn repeated workflows into skills or automations.

18 

19Your history starts only after you choose to turn it on. You control which apps

20and websites contribute, can see and pause collection from the macOS menu bar,

21and can inspect or delete your history at any time.

22 

23Computer History replaces the earlier Chronicle research preview, but it is a

24rebuilt system rather than a rename. Chronicle used screenshots. Computer

25History records interaction events and does not capture your screen or audio.

26 

27<Illustration description="Computer History timeline showing activity summaries, contributing apps, and suggested skills and automations">

28 <ComputerHistoryTimelineIllustration />

29</Illustration>

30 

31## How Computer History helps

32 

33Computer History supplies recent activity as context. When a file, Slack

34conversation, Google Doc, or another source is better for the task, ChatGPT and

35Codex can use the history to identify that source and then read it directly.

36 

37<section class="feature-grid mt-4">

38 

39 

40 

41 

42### Pick up where you left off

43 

44Ask what you were doing before a break without reconstructing every open app,

45document, and next step.

46 

47 

48 

49 

50<ComputerHistoryThreadDemo client:load scenario="resume" />

51 

52</section>

53 

54<section class="feature-grid inverse">

55 

56 

57 

58 

59### Find recent work

60 

61Refer to a document, conversation, or task the way you remember it. Computer

62History can use the activity timeline to identify the source you mean.

63 

64 

65 

66 

67<ComputerHistoryThreadDemo client:load scenario="find" />

68 

69</section>

70 

71<section class="feature-grid">

72 

73 

74 

75 

76### Reuse workflows

77 

78When Computer History notices repeatable work, a timeline entry can suggest a

79skill or automation. Review the suggestion, then ask Codex to create it from the

80recorded workflow.

81 

82 

83 

84 

85<ComputerHistoryThreadDemo client:load scenario="workflow" />

86 

87</section>

88 

89## How Computer History works

90 

91Computer History creates an interaction-event stream from allowed apps and

92websites. Events can include clicks, typing, keyboard shortcuts, app switches,

93and context that macOS exposes through its accessibility system. Computer

94History periodically turns these events into text summaries and local memory

95files.

96 

97Computer History does **not** capture screenshots, screen recordings,

98microphone input, or system audio. Private-mode web browsing activity is never

99included.

100 

101In **Settings > Computer history > History**, the timeline groups summaries by

102day and time. Each item can show:

103 

104- A title and text summary of the activity.

105- The apps that contributed to the summary.

106- A suggested skill or automation when ChatGPT identifies repeatable work.

107- Actions to reveal the memory file in Finder or delete the item.

108 

109Select **Ask about your history** to start a chat with Computer History, or use

110prompts such as:

111 

112- “What was I working on before my last break?”

113- “Where can I find the proposal document I was looking for earlier today?”

114- “Give me a list of tasks I’ve worked on today and their status.”

115- “Prepare a summary of what I did yesterday for standup.”

116 

117## Permissions and access

118 

119Computer History uses separate controls for workspace access, personal opt-in,

120memories, and the apps or websites included in your history:

121 

122- **Workspace access:** Computer History is off by default in Business and

123 Enterprise workspaces and is unavailable until an administrator

124 explicitly grants access. Enterprise administrators can use **Enable Computer

125 History** in [**Workspace Settings > Permissions & roles**](https://chatgpt.com/admin/settings)

126 to grant access to the appropriate workspace roles.

127- **Personal opt-in:** Granting workspace access only lets a member choose to

128 turn on Computer History. It does not turn on the feature for anyone. Each

129 person must opt in individually, including ChatGPT Pro users.

130- **Memories:** Computer History also requires [Memories](https://learn.chatgpt.com/docs/customization/memories).

131 Use `/memories` to control whether an individual chat can use local memories

132 or contribute to future memories.

133- **Apps and websites:** Your app and website permissions determine which

134 sources can contribute interaction events. You can allow only specific

135 sources or exclude apps and website URLs you do not want included.

136 

137If your workspace role does not have access, changing local settings cannot

138enable Computer History.

139 

140## Turn on Computer History

141 

142Computer History is off by default. If you use a Business or Enterprise

143workspace, ask your administrator to grant you access before turning it on.

144Administrator approval does not opt you in.

145 

1461. Open the ChatGPT desktop app on macOS.

1472. In Settings, under **Integrations**, select **Computer history**.

1483. Select **Turn on** and review the privacy, permissions, and local-storage

149 information.

1504. If prompted, turn on **Memories**. Computer History requires Memories so it

151 can use activity context across chats and tasks.

1525. Choose which apps and websites can contribute to your history, then follow

153 any macOS permission prompts.

154 

155Computer History does not require Screen Recording permission. If the setting

156does not appear, confirm that your plan supports Computer History and that your

157workspace administrator has enabled it, if applicable.

158 

159## Control what is included

160 

161You control which apps and websites contribute to future history and whether

162Computer History is actively collecting interaction events.

163 

164### Choose apps and websites

165 

166Under **Settings > Computer history > Permissions**, choose which apps and

167websites Computer History can include:

168 

169- **Exclude these apps** and **Exclude these websites** block the apps or URLs

170 you specify while allowing other supported sources.

171- **Include only these apps** and **Include only these websites** allow only the

172 sources you explicitly choose.

173 

174You can also select an app icon in a history timeline item to exclude that app

175from future history. You can include it again later.

176 

177Private-mode web browsing activity is never included. Changing app or website

178permissions affects future history. To remove existing items, delete or clear

179them.

180 

181### Pause, resume, or stop collection

182 

183Use the Computer History settings or macOS menu bar to control when the feature

184collects activity:

185 

186- Select the ChatGPT icon in the macOS menu bar and expand the Computer History

187 menu to see what activity it captures and access its controls.

188- Select **Pause** to stop collecting new interaction events, or select

189 **Resume** when you are ready to start again.

190- Turn off Computer History to stop future activity collection.

191 

192Computer History can include interaction events from communication apps and

193websites. Turn it off during communications with other people unless you have

194their prior express consent. Consider pausing it or excluding apps that contain

195sensitive health, financial, or personal information.

196 

197## Review and clear history

198 

199Open **Settings > Computer history > History** to inspect what Computer History

200has summarized. You can reveal a summary’s local memory file in Finder, delete

201an individual timeline item, or clear the last 10 minutes, last hour, last day,

202or all history. The macOS menu bar also lets you clear the last session for a

203recent app.

204 

205Clearing history deletes the relevant interaction events and any memories

206created from them. This cannot be undone.

207 

208## Privacy and local storage

209 

210Computer History stores the interaction-event stream temporarily on your Mac so

211ChatGPT and Codex can generate memories and build suggested workflows. It does

212**not** capture screenshots, screen recordings, microphone input, or system

213audio.

214 

215Temporary event files are retained for up to 48 hours. Generated memory files

216remain on your filesystem until you delete or clear them, and you can reveal

217those files from the History timeline.

218 

219### Where does Computer History store my data?

220 

221Computer History saves interaction events temporarily on your Mac. The event

222files are isolated within the ChatGPT

223[App Group](https://developer.apple.com/documentation/xcode/protecting-local-app-data-using-containers),

224which prevents other apps from accessing them without explicit permission.

225ChatGPT and Codex delete these event files after 48 hours.

226 

227Computer History generates the same kind of local memories as Codex: plain-text

228Markdown files that you can read and modify. Those files are stored

229under `$CODEX_HOME/memories/extensions/skysight/`, which typically resolves to

230`~/.codex/memories/extensions/skysight/`.

231 

232 

233 

234 <Alert

235 client:load

236 color="danger"

237 variant="soft"

238 description="Computer History files can contain sensitive information. They are not encrypted by Computer History, and other programs running as your macOS user may be able to access them. Protect your Mac account and exclude sources you do not want included."

239 />

240 

241 

242 

243### What data gets shared with OpenAI?

244 

245Computer History captures interaction events locally, then periodically starts

246an ephemeral Codex session with access to the interaction-event stream to

247summarize your activity into memories.

248 

249OpenAI processes temporary event files on its servers to generate memories,

250which are then stored locally on your Mac. OpenAI does not retain those event

251files after processing unless required by law and does not use them for

252training.

253 

254When ChatGPT or Codex uses a memory in a future chat, relevant memory contents

255and interaction events may be included as context. This chat content may be

256used to improve OpenAI models if allowed by your

257[ChatGPT data controls](https://help.openai.com/en/articles/7730893-data-controls-faq).

258Memories also follow the same

259[chat-level controls as other Codex memories](https://learn.chatgpt.com/docs/customization/memories#control-memories-per-chat).

260 

261### Prompt injection risk

262 

263Computer History increases the risk of prompt injection from content in apps

264and websites. For example, if you visit a website containing malicious

265instructions, ChatGPT or Codex might follow those instructions.

266 

267## Token usage

268 

269Computer History uses tokens while it summarizes activity and creates memories.

270 

271## Troubleshooting

272 

273If Computer History is available but does not start:

274 

2751. Confirm that **Memories** is on.

2762. Open **Settings > Computer history** and select **Finish setup**, **Resume**,

277 or **Try again**, depending on the status shown.

2783. Quit and reopen the ChatGPT desktop app if the setting remains unavailable.

Details

7Codex access tokens are currently supported for ChatGPT Business and7Codex access tokens are currently supported for ChatGPT Business and

8 Enterprise workspaces.8 Enterprise workspaces.

9 9 

10Access tokens are created in the ChatGPT admin console at [Access tokens](https://chatgpt.com/admin/access-tokens). They're tied to the ChatGPT user who creates them and that user's workspace. The tokens act as agent identities for programmatic local workflows.10Personal access tokens created from the ChatGPT admin console's [Access tokens](https://chatgpt.com/admin/access-tokens) page are tied to the ChatGPT user who creates them and that user's workspace. The tokens act as agent identities for programmatic local workflows. For tokens created from a dedicated non-human workspace identity's detail page, see [Service accounts](https://learn.chatgpt.com/docs/enterprise/service-accounts).

11 11 

12If a Platform API key works for your automation, keep using API key auth. Use12If a Platform API key works for your automation, keep using API key auth. Use

13 Codex access tokens when a trusted local workflow specifically needs ChatGPT13 Codex access tokens when a trusted local workflow specifically needs ChatGPT


185## Related docs185## Related docs

186 186 

187- [Authentication](https://learn.chatgpt.com/docs/auth)187- [Authentication](https://learn.chatgpt.com/docs/auth)

188- [Service accounts](https://learn.chatgpt.com/docs/enterprise/service-accounts)

188- [Non-interactive mode](https://learn.chatgpt.com/docs/non-interactive-mode)189- [Non-interactive mode](https://learn.chatgpt.com/docs/non-interactive-mode)

189- [Admin rollout guide](https://learn.chatgpt.com/docs/enterprise/admin-setup)190- [Admin rollout guide](https://learn.chatgpt.com/docs/enterprise/admin-setup)

190- [Groups and provisioning](https://learn.chatgpt.com/docs/enterprise/groups-and-provisioning)191- [Groups and provisioning](https://learn.chatgpt.com/docs/enterprise/groups-and-provisioning)

Details

48- [Configure role-based access control](https://help.openai.com/en/articles/11750701-rbac)48- [Configure role-based access control](https://help.openai.com/en/articles/11750701-rbac)

49- [Manage groups](https://help.openai.com/en/articles/9083985-group-permissions-in-gpts)49- [Manage groups](https://help.openai.com/en/articles/9083985-group-permissions-in-gpts)

50 50 

51### Control Computer History access

52 

53[Computer History](https://learn.chatgpt.com/docs/customization/computer-history) is off by default for

54Business and Enterprise workspaces. Members cannot turn it on until an

55administrator explicitly grants access. Enterprise administrators can grant

56access by role:

57 

581. Open [**Workspace Settings > Permissions & roles**](https://chatgpt.com/admin/settings).

592. Find **Computer History** and choose the workspace role that should have

60 access.

613. Turn on **Enable Computer History** for that role.

62 

63This permission only allows assigned members to turn on Computer History; it

64does not turn on the feature for them. Each member must opt in from the ChatGPT

65desktop app on macOS and can choose which apps and websites contribute. Members

66without the required workspace permission cannot enable the feature through

67local settings.

68 

51## Apply local runtime policy69## Apply local runtime policy

52 70 

53Local runtime policy constrains covered capabilities in the ChatGPT desktop71Local runtime policy constrains covered capabilities in the ChatGPT desktop

enterprise/service-accounts.md +156 −0 created

Details

1# Service accounts

2 

3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

4 

5Service accounts let you run and scale headless Codex workflows across your organization without relying on an employee's account. Each continuous integration (CI) runner, scheduled job, or shared integration gets its own ChatGPT workspace identity, with the same groups, roles, access controls, and auditability you expect for people.

6 

7Only workspace owners and admins can create service accounts. They can let other people or groups manage an account, configure plugins, or create access tokens.

8 

9Service accounts are available only on pay-as-you-go plans.

10 

11A service account represents a non-human workspace identity. A [personal access token](https://learn.chatgpt.com/docs/enterprise/access-tokens) represents the workspace member who creates it. API Platform project service accounts and API keys use separate project access and billing.

12 

13## Create and set up a service account

14 

15This interactive walkthrough uses GitHub as an example: create an account, configure a plugin, create a token, and assign groups and roles.

16 

17<ServiceAccountsDemo client:load guided />

18 

191. Open [Service accounts](https://chatgpt.com/admin/service-accounts) in your workspace settings.

202. Select the plus (**+**) button and enter a descriptive name, such as `release-automation`.

213. Select **Create**.

22 

23## Connect a plugin

24 

25Configure plugins for the service account itself. It doesn't inherit the creator's plugins or connected apps.

26 

271. Open the account's **Plugins** section and select **Add plugin**.

282. Choose a plugin and confirm that it shows as configured or enabled.

29 

30The **Configure** and **Manager** roles can set up plugins. The **User** role can't.

31 

32## Create an access token

33 

34Create a token from the service account's detail page. The token represents the service account, not the person who creates it.

35 

361. Open the account and select **Create token** in **Access tokens**.

372. Name the token, confirm the **Codex** scope, and choose an expiration.

383. Select **Create** and save the token in your secret manager.

39 

40The full token appears only once. Workspace policies control which expirations are available.

41 

42## Assign roles and groups

43 

44A service account can receive workspace roles and join groups like a human workspace member. Assign its access directly; it doesn't inherit the creator's permissions.

45 

46To let people or groups manage the account, select **Share**, then **Add people or groups**, and assign a role:

47 

48| Shared-account role | Configure the account and its plugins | Create service-account access tokens |

49| ------------------- | ------------------------------------- | ------------------------------------ |

50| **User** | No | Yes |

51| **Configure** | Yes | No |

52| **Manager** | Yes | Yes |

53 

54These roles apply to people managing the account. They are separate from the workspace roles and groups assigned to the service account.

55 

56**Configure** and **Manager** can enable or disable the account. Only workspace owners and admins can create, delete, or share accounts. Operators manage shared accounts while signed in to their own ChatGPT accounts.

57 

58For more about workspace permissions, see [Roles and workspace permissions](https://learn.chatgpt.com/docs/enterprise/roles-and-workspace-permissions).

59 

60## Run Codex without signing in

61 

62Service-account access tokens require Codex CLI version `0.142.0` or later. Set `CODEX_ACCESS_TOKEN` and run Codex without opening a browser:

63 

64```bash

65export CODEX_ACCESS_TOKEN="<service-account-access-token>"

66codex exec --json "Inspect this repository and summarize its current state."

67```

68 

69In CI, provide the token through a secret manager or runner secret.

70 

71To save a login on a trusted machine, pass the token through standard input:

72 

73```bash

74printf '%s' "$CODEX_ACCESS_TOKEN" | codex login --with-access-token

75codex exec "Summarize the changes in the current branch."

76```

77 

78This saves the credential locally. On shared or temporary runners, use `CODEX_ACCESS_TOKEN` without saving a login.

79 

80## Provision service accounts with SCIM

81 

82If your workspace supports service-account provisioning through the System for Cross-domain Identity Management (SCIM) protocol, set `userType` to `ServiceAccount` in your identity provider:

83 

84```json

85{

86 "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],

87 "userName": "svc-codex-release@company.example",

88 "displayName": "Codex release automation",

89 "active": true,

90 "userType": "ServiceAccount"

91}

92```

93 

94Assign the identity to the workspace and required groups, then sync it. The identity provider manages the account's name, group membership, and lifecycle. SCIM-managed accounts can't be renamed or deleted in ChatGPT. See [Groups and provisioning](https://learn.chatgpt.com/docs/enterprise/groups-and-provisioning).

95 

96## Manage service accounts with the Admin API

97 

98If your workspace has access, use a ChatGPT Admin API key to manage accounts, tokens, and sharing. Read operations require `chatgpt.enterprise.service_account.read`; changes require `chatgpt.enterprise.service_account.write`. A service-account token can't authenticate Admin API requests.

99 

100Check the authenticated [Admin API reference](https://chatgpt.com/admin/api-reference) for available operations and current request paths.

101 

102### Accounts

103 

104| Operation | Method | What it does |

105| ---------------------------- | -------- | ------------------------------------------ |

106| List accounts | `GET` | Returns workspace service accounts |

107| Create an account | `POST` | Creates a named service account |

108| Get an account | `GET` | Returns one service account |

109| Enable or disable an account | `PATCH` | Updates the account's `enabled` value |

110| Delete an account | `DELETE` | Removes the account and revokes its tokens |

111 

112Create accounts with `POST /v1/manage/workspaces/{workspace_id}/service-accounts`. Account updates change only `enabled`.

113 

114### Tokens

115 

116| Operation | Method | What it does |

117| -------------- | -------- | ------------------------------------ |

118| List tokens | `GET` | Returns the account's token metadata |

119| Create a token | `POST` | Creates a scoped access token |

120| Revoke a token | `DELETE` | Permanently revokes one token |

121 

122For example, create a Codex token that expires after 30 days:

123 

124```json

125{

126 "name": "production-release-runner",

127 "ttl": 2592000,

128 "scopes": ["chatgpt.workspace.feature.allow-codex-local-access.access"]

129}

130```

131 

132`ttl` is the token lifetime in seconds. A finite lifetime must be less than one year and follow your workspace's expiration policy. The full `access_token` is returned only when the token is created.

133 

134The Admin API can also list, add, update, and remove shared-account access. Its role values are `manager`, `configurer`, and `user`; `configurer` appears as **Configure** in ChatGPT.

135 

136## Secure and manage service accounts

137 

138- Grant only the roles, groups, plugins, and connections the workflow needs.

139- Store tokens in a secret manager and use trusted runners.

140- Keep credentials out of logs, chat messages, and source control.

141- Set finite expirations and review account access and activity regularly.

142- Rotate a token by creating a replacement, updating the workflow, verifying access, and revoking the old token in the workspace or Admin API.

143- Revoke exposed tokens immediately and investigate the account's recent activity.

144- Disable or delete unused accounts in the workspace or Admin API. Both actions revoke all active tokens. Disabled accounts can be re-enabled with new tokens; deletion can't be undone.

145 

146Runs are attributed to the service account. Available workspace analytics and audit records can also identify who created tokens or changed account settings. Confirm event coverage in the authenticated [Admin API reference](https://chatgpt.com/admin/api-reference).

147 

148## Related docs

149 

150- [Authentication](https://learn.chatgpt.com/docs/auth)

151- [Personal access tokens](https://learn.chatgpt.com/docs/enterprise/access-tokens)

152- [Roles and workspace permissions](https://learn.chatgpt.com/docs/enterprise/roles-and-workspace-permissions)

153- [Groups and provisioning](https://learn.chatgpt.com/docs/enterprise/groups-and-provisioning)

154- [Governance](https://learn.chatgpt.com/docs/enterprise/governance)

155- [Compliance API and audit events](https://learn.chatgpt.com/docs/enterprise/compliance-api)

156- [Non-interactive mode](https://learn.chatgpt.com/docs/non-interactive-mode)

glossary.md +3 −3

Details

120 "Authentication using a ChatGPT account and workspace permissions.",120 "Authentication using a ChatGPT account and workspace permissions.",

121 },121 },

122 {122 {

123 key: "Chronicle",123 key: "Computer History",

124 href: "/codex/customization/chronicle",124 href: "/codex/customization/computer-history",

125 appliesTo: "Desktop app",125 appliesTo: "Desktop app",

126 description:126 description:

127 "Opt-in feature that builds memories from recent screen context.",127 "Opt-in macOS feature that builds memories and a timeline from interaction events across allowed apps and websites.",

128 },128 },

129 {129 {

130 key: "Cloud",130 key: "Cloud",

memories.md +3 −2

Details

50 50 

51<ContentModeSwitch group="codex-surface" id="app">51<ContentModeSwitch group="codex-surface" id="app">

52 52 

53[Chronicle](https://learn.chatgpt.com/docs/customization/chronicle) is a desktop-only feature that helps53[Computer History](https://learn.chatgpt.com/docs/customization/computer-history) is a macOS desktop

54Codex recover recent working context from your screen to build up memory.54feature that turns activity across allowed apps and websites into memories and

55a timeline that ChatGPT and Codex can reference.

55 56 

56</ContentModeSwitch>57</ContentModeSwitch>

57 58 

memories/chronicle.md +0 −201 deleted

File Deleted View Diff

1# Chronicle

2 

3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

4 

5Chronicle is in an **opt-in research preview**. It is only available for

6 ChatGPT Pro subscribers on macOS. Please review the [Privacy and

7 Security](#privacy-and-security) section for details and to understand the

8 current risks before enabling.

9 

10Chronicle augments Codex memories with context from your screen. When you prompt

11Codex, those memories can help it understand what you’ve been working on with

12less need for you to restate context.

13 

14Chronicle is available as an opt-in research preview in the ChatGPT desktop app on macOS.

15It requires macOS Screen Recording and Accessibility permissions. Before

16enabling, be aware that Chronicle uses rate limits quickly, increases risk of

17prompt injection, and stores memories unencrypted on your device.

18 

19## How Chronicle helps

20 

21We’ve designed Chronicle to reduce the amount of context you have to restate

22when you work with Codex. By using recent screen context to improve memory

23building, Chronicle can help Codex understand what you’re referring to, identify

24the right source to use, and pick up on the tools and workflows you rely on.

25 

26<section class="feature-grid mt-4">

27 

28 

29 

30 

31### Use what’s on screen

32 

33With Chronicle Codex can understand what you are currently looking at, saving

34you time and context switching.

35 

36 

37 

38 

39<ChronicleThreadDemo client:load scenario="screen" />

40 

41</section>

42 

43<section class="feature-grid inverse">

44 

45 

46 

47 

48### Fill in missing context

49 

50No need to carefully craft your context and start from zero. Chronicle lets

51Codex fill in the gaps in your context.

52 

53 

54 

55 

56<ChronicleThreadDemo client:load scenario="project" />

57 

58</section>

59 

60<section class="feature-grid">

61 

62 

63 

64 

65### Remember tools and workflows

66 

67No need to explain to Codex which tools to use to perform your work. Codex

68learns as you work to save you time in the long run.

69 

70 

71 

72 

73<ChronicleThreadDemo client:load scenario="tools" />

74 

75</section>

76 

77In these cases, Codex uses Chronicle to provide additional context. When another

78source is better for the job, such as reading the specific file, Slack thread,

79Google Doc, dashboard, or pull request, Codex uses Chronicle to identify the

80source and then use that source directly.

81 

82## Enable Chronicle

83 

841. Open Settings in the ChatGPT desktop app.

852. Go to **Personalization** and make sure **Memories** is enabled.

863. Turn on **Chronicle** below the Memories setting.

874. Review the consent dialog and choose **Continue**.

885. Grant macOS Screen Recording and Accessibility permissions when prompted.

896. When setup completes, choose **Try it out** or start a new chat.

90 

91If macOS reports that Screen Recording or Accessibility permission is denied,

92open System Settings &gt; Privacy & Security &gt; Screen Recording or

93Accessibility and enable ChatGPT. If a permission is restricted by macOS or

94your organization, Chronicle will start after the restriction is removed and

95ChatGPT receives the required permission.

96 

97## Pause or disable Chronicle at any time

98 

99You control when Chronicle generates memories using screen context. Use the

100ChatGPT menu bar icon to choose **Pause Chronicle** or **Resume Chronicle**. Pause

101Chronicle before meetings or when viewing sensitive content that you do not want

102Codex to use as context. To disable Chronicle, return to **Settings &gt;

103Personalization &gt; Memories** and turn off **Chronicle**.

104 

105You can also control whether memories are used in a given chat. [Learn

106more](https://learn.chatgpt.com/docs/customization/memories#control-memories-per-chat).

107 

108## Rate limits

109 

110Chronicle works by running sandboxed agents in the background to generate

111memories from captured screen images. These agents currently consume rate limits

112quickly.

113 

114## Privacy and security

115 

116Chronicle uses screen captures, which can include sensitive information visible

117on your screen. It does not have access to your microphone or system audio.

118Don’t use Chronicle to record meetings or communications with others without

119their consent. Pause Chronicle when viewing content you do not want remembered

120in memories.

121 

122### Where does Chronicle store my data?

123 

124Screen captures are ephemeral and will only be saved temporarily on your

125computer. Temporary screen capture files may appear under

126`$TMPDIR/chronicle/screen_recording/` while Chronicle is running. Screen captures

127that are older than 6 hours will be deleted while Chronicle is running.

128 

129The memories that Chronicle generates are just like other Codex memories:

130unencrypted markdown files that you can read and modify if needed. You can also

131ask Codex to search them. If you want to have Codex forget something you can

132delete the respective file inside the folder or selectively edit the markdown

133files to remove the information you’d like to remove. You should not manually

134add new information. The generated Chronicle memories are stored locally on your

135computer under `$CODEX_HOME/memories_extensions/chronicle/` (typically

136`~/.codex/memories_extensions/chronicle`).

137 

138 

139 

140 <Alert

141 client:load

142 color="danger"

143 variant="soft"

144 description="Both directories for your screen captures and memories might contain sensitive information. Make sure you do not share content with others, and be aware that other programs on your computer can also access these files."

145 />

146 

147 

148 

149### What data gets shared with OpenAI?

150 

151Chronicle captures screen context locally, then periodically uses Codex to

152summarize recent activity into memories. To generate those memories, Chronicle

153starts an ephemeral Codex session with access to this screen context. That

154session may process selected screenshot frames, OCR text extracted from

155screenshots, timing information, and local file paths for the relevant time

156window.

157 

158Screen captures used for memory generation are stored temporarily on your device. They are processed on our

159servers to generate memories, which are then stored locally on device. We do not

160store the screenshots on our servers after processing unless required by law,

161and do not use them for training.

162 

163The generated memories are Markdown files stored locally under

164`$CODEX_HOME/memories_extensions/chronicle/`. When Codex uses memories in a

165future session, relevant memory contents may be included as context for that

166session, and may be used to improve our models if allowed in your ChatGPT

167settings. [Learn more](https://help.openai.com/en/articles/7730893-data-controls-faq).

168 

169## Prompt injection risk

170 

171Using Chronicle increases risk to prompt injection attacks from screen content.

172For instance, if you browse a site with malicious agent instructions, Codex may

173follow those instructions.

174 

175## Troubleshooting

176 

177### How do I enable Chronicle?

178 

179If you do not see the Chronicle setting, make sure you are using a ChatGPT desktop app

180build that includes Chronicle and that you have Memories enabled inside Settings

181&gt; Personalization.

182 

183Chronicle is currently only available for ChatGPT Pro subscribers on macOS.

184 

185If setup does not complete:

186 

1871. Confirm that ChatGPT has Screen Recording and Accessibility permissions.

1882. Quit and reopen the ChatGPT desktop app.

1893. Open **Settings > Personalization** and check the Chronicle status.

190 

191### Which model is used for generating the Chronicle memories?

192 

193Chronicle uses the same model as your other [Memories](https://learn.chatgpt.com/docs/customization/memories). If you

194did not configure a specific model it uses your default Codex model. To choose a

195specific model, update the `consolidation_model` in your

196[configuration](https://learn.chatgpt.com/docs/config-file/config-basic).

197 

198```toml

199[memories]

200consolidation_model = "gpt-5.6-luna"

201```

personalize.md +8 −7

Details

30Memories are separate from required project guidance. Keep instructions that30Memories are separate from required project guidance. Keep instructions that

31must always apply in `AGENTS.md` or checked-in project documentation.31must always apply in `AGENTS.md` or checked-in project documentation.

32 32 

33## Add recent screen context with Chronicle33## Add recent activity with Computer History

34 34 

35[Chronicle](https://learn.chatgpt.com/docs/customization/chronicle) is an opt-in research preview that can35[Computer History](https://learn.chatgpt.com/docs/customization/computer-history) is an opt-in macOS

36augment memories with recent screen context. It's available to eligible36desktop feature that can turn activity across allowed apps and websites into

37ChatGPT Pro subscribers in the macOS desktop app and requires Screen Recording37memories and a timeline. It records interaction events rather than screenshots

38and Accessibility permissions.38or audio.

39 39 

40Review Chronicle's privacy, security, storage, and rate-limit considerations40Review what Computer History includes before enabling it. You can pause it,

41before enabling it. You can pause or disable Chronicle at any time.41exclude apps and websites, inspect or delete individual timeline items, and

42clear recent or all history at any time.

42 43 

43## Manage personalization44## Manage personalization

44 45 

whats-new.md +61 −0

Details

6work, with examples and links to learn more. For every versioned update, bug fix,6work, with examples and links to learn more. For every versioned update, bug fix,

7and minor improvement, see the [Codex changelog](https://learn.chatgpt.com/docs/changelog).7and minor improvement, see the [Codex changelog](https://learn.chatgpt.com/docs/changelog).

8 8 

9## August 10–14, 2026

10 

11### Find earlier work with Computer History

12 

13[Computer History](https://learn.chatgpt.com/docs/customization/computer-history) turns activity across

14your apps and websites into a searchable timeline and memories that ChatGPT

15and Codex can use. Turn it on only if you want to share that context, then

16choose which apps and websites contribute, pause collection, and review or

17delete your history at any time.

18 

19Computer History is available in the ChatGPT desktop app on macOS for ChatGPT

20Pro, Business, and Enterprise customers. Business and Enterprise

21administrators must first enable access. Initial availability excludes the

22European Union, Switzerland, and the United Kingdom.

23 

24 

25 

26**Prompt:**

27 

28```text

29Find the document and Slack thread I was reviewing earlier, then summarize the decisions I still need to act on.

30```

31 

32### Use the ChatGPT desktop app on Linux

33 

34The [ChatGPT desktop app for Linux](https://learn.chatgpt.com/docs/linux/linux-app) is now available in

35preview. Install a `.deb` package on supported Ubuntu or Debian distributions,

36or an `.rpm` package on Fedora. Packages are available for both x64 and ARM64

37processors.

38 

39Sign in with your ChatGPT account to work with projects, local files, and

40Codex. Some features, including Computer Use, aren't yet available in the

41Linux preview.

42 

43### Bring your existing agent setup and work with you

44 

45[Import instructions, settings, skills, plugins, projects, and recent

46work](https://learn.chatgpt.com/docs/import) from **Claude Code**, **Claude Cowork**, or

47**Cursor** into the ChatGPT desktop app. Turn on automatic updates in

48**Settings > Import** to keep your imported work in sync.

49 

50In Codex CLI, use `/import` to bring supported setup and recent chats from

51Claude Code or Cursor into your local session.

52 

53[Read the August 11 desktop and CLI release

54notes](https://learn.chatgpt.com/docs/changelog#codex-2026-08-11-app).

55 

56### Choose the right access for defensive security work

57 

58Daybreak now offers two tiers for approved defenders. **Daybreak Blue** supports

59general defensive work, such as secure code review, incident response, and

60patch validation. **Daybreak Red** requires its own approval and provides

61access to purpose-trained models for authorized security assessments.

62 

63Access requires [Trusted Access for

64Cyber](https://learn.chatgpt.com/docs/cyber-safety#trusted-access-for-cyber) and applies only to the

65approved identity, workspace or organization, model, and product surface.

66 

67[Read the August 10 Daybreak

68announcement](https://learn.chatgpt.com/docs/changelog#codex-2026-08-10-daybreak).

69 

9## August 3–7, 202670## August 3–7, 2026

10 71 

11### Talk through files and projects with ChatGPT Voice72### Talk through files and projects with ChatGPT Voice