The Codex desktop app freezes when handling large rollout/history JSONL files, causing unresponsiveness during long-running sessions.
The Codex desktop app freezes when handling large rollout/history JSONL files, causing unresponsiveness during long-running sessions.
Problem statement normalized from the linked evidence
CANDIDATE VIEW · NOT A PUBLISHED OPPORTUNITY
01
Qualification checklist
Gate decision: Aug 15, 2026
×
At least 3 independent users2 / 3
NOT MET
✓
At least 2 independent discussions2 / 2
MET
✓
At least 1 supporting signal2 Workarounds · 2 Blocked workflows · Persistence
MET
02
Observed signals
Users2
Discussions2
Mentions2
Active days2
Source coverageGitHub
TrendUNKNOWN
First seenMay 03, 2026
Last seenMay 16, 2026
Why the gate is holding
Fewer than 3 independent users
Competition research, commercial scoring, and Build Gap analysis do not run until this gate passes.
03
Source evidence
2 evidence records
github · HIGH · May 16, 2026
Codex app can freeze with very large rollout/history JSONL files
### Component Codex desktop app ### What happened? When a Codex conversation runs for a long time, the local rollout/history JSONL file can grow to hundreds of MB. I have several sessions that are around 500 MB or larger. When I continue working with those long-running sessions in the Codex desktop app, the app can freeze for a noticeable amount of time, especially when sending a new prompt. I suspect the hot path may be doing too much work over the full session history file, or otherwise synchronously processing m…
Codex Desktop App becomes laggy because it scans all `~/.codex/sessions` rollout files instead of respecting Desktop-visible session index/state
### What version of the Codex App are you using (From “About Codex” dialog)? Version 26.429.30905 (2345) ### What subscription do you have? Pro and Business ### What platform is your computer? Darwin 25.3.0 arm64 arm ### What issue are you seeing? ## Summary Codex Desktop App becomes slow/unresponsive when `~/.codex/sessions` contains many rollout JSONL files. The important point: these session files are not only created by Codex Desktop. They are also created by other Codex clients that share the same `CODEX_HOME`…