GitHub issue #20864 in openai/codex, opened 2026-05-03 by 8th-block, records a report that Codex Desktop App becomes slow/unresponsive when ~/.codex/sessions contains many rollout JSONL files — 109 files totalling 78M in the reporter's case, against 22 entries in session_index.jsonl; the report says Desktop appears to scan/read the entire sessions folder even though session_index.jsonl contains the much smaller Desktop-visible set, and clearing or moving files out of ~/.codex/sessions immediately fixes the lag; the report was filed against Codex Desktop App 26.429.30905 on macOS (Apple Silicon).
Verbatim Excerpts from Cited Records
“Codex Desktop App becomes slow/unresponsive when `~/.codex/sessions` contains many rollout JSONL files.”
·
openai/codex (issue 20864 opening body, What issue are you seeing? section)
·
2026-05-03T11:34:25Z
·GitHub Issue ↗
“Desktop appears to scan/read the entire `~/.codex/sessions` folder, even though `~/.codex/session_index.jsonl` contains a much smaller set of sessions that seem to be the intended Desktop-visible history.”
·
openai/codex (issue 20864 opening body, What issue are you seeing? section)
·
2026-05-03T11:34:25Z
·GitHub Issue ↗
“Clearing or moving files out of `~/.codex/sessions` immediately fixes the Desktop UI lag.”
·
openai/codex (issue 20864 opening body, What issue are you seeing? section)
·
2026-05-03T11:34:25Z
·GitHub Issue ↗
“The Desktop UI should not degrade just because other Codex clients share the same `CODEX_HOME`.”
·
openai/codex (issue 20864 opening body, Additional information section)
·
2026-05-03T11:34:25Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 24 comments were read. github-actions[bot] (2026-05-03) flagged potential duplicates #20802, #19517, #20103, #19483 and #20269. etraut-openai (2026-05-03, OpenAI) responded that all clients share state_5.sqlite and should not need to scan the sessions directory, suggesting database corruption or files manipulated behind Codex's back; the reporter disputed the corruption explanation. Multiple users confirmed the lag on later builds and other platforms through 2026-11-18, including john0123412 (Windows), helenananaa (Windows, GPT-5.6 Ultra subagent fan-out), drkvj (macOS, fresh restart) and leventov (2026-11-18, traced a related history-search path in the Linux CLI 0.170.0). No maintainer fix merged and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #20864 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.