{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvslz67n7fh3gibheazemesv6y5cy5xp7rabegguuljsfhmuyg6m",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlsdi56t6hu2"
  },
  "path": "/t/codex-chronicle-generated-572-background-summaries-overnight-and-consumed-quota/1380899#post_1",
  "publishedAt": "2026-05-14T06:57:47.000Z",
  "site": "https://community.openai.com",
  "textContent": "I am posting this here because the forum banner explicitly allows Codex developer-tool discussion, and this appears to be a Codex background-task bug.\n\nAfter enabling Chronicle in the Codex desktop app, my local machine generated a large number of persisted Chronicle memory summaries during non-working hours. This appears to have consumed my 20x usage quota without explicit user turns.\n\nEvidence summary:\n\n  * Date/time zone: 2026-05-14, Beijing time\n  * Chronicle resource location: ~/.codex/memories/extensions/chronicle/resources\n  * Total persisted Chronicle summaries generated that day: 572\n  * Time range: 2026-05-14 00:00:00 to 2026-05-14 11:40:00 Beijing time\n  * Records generated before the visible 11:30:16 Chronicle launch: 571\n  * From 00:00 to 09:00 Beijing time, Chronicle generated 60 summaries per hour, i.e. one persisted file per minute, even though the files are named 10min-memory-summary.\n\n\n\nHourly count:\n\n```text\n60 2026-05-14 00:00\n60 2026-05-14 01:00\n60 2026-05-14 02:00\n60 2026-05-14 03:00\n60 2026-05-14 04:00\n60 2026-05-14 05:00\n60 2026-05-14 06:00\n60 2026-05-14 07:00\n60 2026-05-14 08:00\n30 2026-05-14 09:00\n2 2026-05-14 11:00\n```\n\nDirect log evidence shows automatic summary sessions:\n\n```text\n2026-05-14T03:30:16.739Z … codex_chronicle starting\n2026-05-14T03:30:16.783Z … screen recording starting\n2026-05-14T03:40:36.867Z … starting summary session … level=“10min” bucket=2026-05-14T03-30-00Z\n2026-05-14T03:40:36.868Z … starting codex exec summary session … model=gpt-5.5 reasoning_effort=medium\n2026-05-14T03:42:36.890Z … starting summary session … level=“10min” bucket=2026-05-14T03-30-00Z\n2026-05-14T03:42:36.891Z … starting codex exec summary session … model=gpt-5.5 reasoning_effort=medium\n```\n\nThe logs also show repeated screen-recording permission failures while Chronicle was active:\n\n```text\nERROR screen recording reconcile failed kind=PermissionRequired state=Unsupported\nNo shareable content available: Content unavailable: user denied TCC screen capture\n```\n\nWhy this looks like a bug:\n\n  1. The persisted summary files show one 10min-memory-summary per minute for long periods.\n  2. 571 persisted summaries existed before the visible 11:30:16 Chronicle process launch.\n  3. Logs show repeated automatic codex exec summary sessions using gpt-5.5.\n  4. Logs also show repeated screen-capture permission failures, but Chronicle still started or retried summary-related work.\n  5. This background behavior appears to consume quota without explicit user requests.\n\n\n\nI have also submitted this through OpenAI Help Center and asked support to investigate and restore/refund the consumed quota. I can provide screenshots, the full exported TSV record list, and local log excerpts privately if OpenAI staff need them.",
  "title": "Codex Chronicle generated 572 background summaries overnight and consumed quota"
}