[macOS][Computer History] Recorder creates Skysight segments but 10-minute summaries never start
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT desktop 26.818.61809 (build 7019)
Additional bundled versions:
Computer History plugin: 1.0.1000854
Bundled CLI: codex-cli 0.149.0-alpha.4.3
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
Computer History has remained empty after being enabled for several days. The settings page continues to show:
No computer history yet
The recording stage itself is working:
- Computer History reports
state=running. SkyComputerUseServiceis running.- Fresh event-stream segments continue to appear under the Skysight segment directory.
- The effective observation settings use
observeas the default for both applications and URLs, with empty allowlists and blocklists.
However, no memory summary is ever written. At the latest check:
Skysight event-stream segment directories: 55
~/.codex/memories/extensions/skysight/resources files: 0
The current segment started normally at 2026-08-24T11:20:00Z, and the recording session had been running since 2026-08-24T10:43:31Z after the latest restart. Multiple complete 10-minute windows passed without a single 10min summary file.
Fully quitting and reopening ChatGPT did not resolve the problem. Updating the app from 26.818.41509 (build 6962) to 26.818.61809 (build 7019) also did not resolve it.
The updated application contains Contents/Resources/codex_chronicle, but the summarization stage does not produce output. This appears to be a scheduler or helper-launch failure after successful event capture, rather than a screen-recording permission or observation-filter failure.
What steps can reproduce the bug?
-
Enable Computer History in ChatGPT desktop on macOS.
-
Leave the application running and use the computer normally for longer than several 10-minute summary windows.
-
Confirm that Computer History reports
runningand that new directories appear under:~/Library/Group Containers/2DC432GLL2.com.openai.sky.CUAService/Library/Caches/ComputerUse/Skysight/segments/ -
Count the recorded segments and generated summaries:
find "$HOME/Library/Group Containers/2DC432GLL2.com.openai.sky.CUAService/Library/Caches/ComputerUse/Skysight/segments" \ -mindepth 1 -maxdepth 1 -type d | wc -l find "$HOME/.codex/memories/extensions/skysight/resources" \ -type f | wc -l -
Observe that segment count continues to increase while the resources count remains zero.
-
Open Settings → Computer History and observe that the History panel still says
No computer history yet.
Actual result from the latest check:
55 segments
0 summary resources
The issue persists after a full application restart and update.
What is the expected behavior?
After eligible activity has been captured for a complete summary window:
- the background summarizer should start;
- at least one
10minMarkdown summary should be written under~/.codex/memories/extensions/skysight/resources/; - the Computer History UI should show generated history instead of remaining permanently empty;
- if summary generation cannot start, the UI or diagnostics should expose a specific actionable error rather than reporting the feature as running.
Acceptance Criteria
- When eligible Skysight segments cover a complete 10-minute window, the 10-minute summary job is queued and completes.
- A successful job writes a
10minMarkdown resource under~/.codex/memories/extensions/skysight/resources/and makes the result visible in Computer History. - If the job cannot be queued or launched, diagnostics expose the failing scheduler/helper stage and an actionable error.
- Recording-only operation cannot remain silently reported as a healthy end-to-end Computer History state indefinitely.
Validation
- Add a regression test covering recorder output followed by 10-minute summary scheduling.
- Verify the path on macOS with default-observe settings and empty allowlists/blocklists.
- Verify that a summarizer launch failure is surfaced without stopping or corrupting the raw event stream.
Additional information
- macOS Screen & System Audio Recording permission is enabled for ChatGPT.
- Application and website permission lists load successfully.
- The bundled
codex_chronicleexecutable is present. - A read-only diagnostic run reported zero failed checks. Its warnings concerned unrelated endpoint-protection inspection, Gatekeeper assessment, and local thread-inventory findings.
- No raw event-stream contents are included because they may contain private on-screen activity.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Computer History path from Skysight segment directories to the bundled Contents/Resources/codex_chronicle helper and the resources directory at ~/.codex/memories/extensions/skysight/resources. Reproduce the 55-segment, zero-summary state and inspect where 10-minute scheduling or helper launch stops. Done means a regression test covers scheduling, a 10min Markdown resource appears, and launch failures expose an actionable diagnostic without stopping recording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100