codex - 💡(How to fix) Fix Windows Codex Desktop sidebar hides valid local project threads while SQLite and rollout files are intact [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20254Fetched 2026-04-30 06:31:02
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2closed ×1

Code Example

%USERPROFILE%\.codex\state_5.sqlite
threads_total=111
threads_unarchived=110

%USERPROFILE%\.codex\session_index.jsonl
session_index_lines=139
session_index_unique_ids=111

%USERPROFILE%\.codex\sessions
session_rollout_files=110

%USERPROFILE%\.codex\archived_sessions
archived_rollout_files=1

---

Project A: 3 unarchived threads in SQLite, 2 visible in sidebar, 1 hidden
Project B: 13 unarchived threads in SQLite, 5 visible in sidebar, 8 hidden
Project C: 33 unarchived threads in SQLite, 20 visible in sidebar, 13 hidden
Project D: 19 unarchived threads in SQLite, 4 visible in sidebar, 15 hidden
Project E: 2 unarchived threads in SQLite, 1 visible in sidebar, 1 hidden
Project F: 38 unarchived threads in SQLite, 15 visible in sidebar, 23 hidden

---

SQLite has 38 active threads for the project.
The sidebar shows about 15 project threads.
Threads ranked below the visible window are not shown in the left sidebar.
After restoring/cloning older threads so that they become recent, those restored threads appear near the top, but other previously visible threads move below the visible window and disappear from the sidebar.

---

Some threads.cwd values use plain C:\...
Some threads.cwd values use \\?\C:\...
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From "About Codex" dialog)?

26.422.8496.0

Local executable diagnostics also show codex.exe version 0.126.0.0.

What subscription do you have?

Paid OpenAI account.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop on Windows is not showing all local, unarchived project threads in the left sidebar. The underlying local data still exists in the Codex store, but the sidebar appears to render only a limited window of threads per project. When older threads are made recent or cloned/restored, they appear near the top, but other previously visible threads are pushed out of the visible sidebar list.

This looks like a sidebar enumeration/rendering bug rather than local data loss.

Local diagnostics:

%USERPROFILE%\.codex\state_5.sqlite
threads_total=111
threads_unarchived=110

%USERPROFILE%\.codex\session_index.jsonl
session_index_lines=139
session_index_unique_ids=111

%USERPROFILE%\.codex\sessions
session_rollout_files=110

%USERPROFILE%\.codex\archived_sessions
archived_rollout_files=1

Observed sidebar/project counts after a restart:

Project A: 3 unarchived threads in SQLite, 2 visible in sidebar, 1 hidden
Project B: 13 unarchived threads in SQLite, 5 visible in sidebar, 8 hidden
Project C: 33 unarchived threads in SQLite, 20 visible in sidebar, 13 hidden
Project D: 19 unarchived threads in SQLite, 4 visible in sidebar, 15 hidden
Project E: 2 unarchived threads in SQLite, 1 visible in sidebar, 1 hidden
Project F: 38 unarchived threads in SQLite, 15 visible in sidebar, 23 hidden

The hidden threads are not archived. Their thread rows exist in state_5.sqlite; corresponding entries exist in session_index.jsonl; and their rollout JSONL files still exist under %USERPROFILE%\.codex\sessions.

The behavior is especially visible in Project F:

SQLite has 38 active threads for the project.
The sidebar shows about 15 project threads.
Threads ranked below the visible window are not shown in the left sidebar.
After restoring/cloning older threads so that they become recent, those restored threads appear near the top, but other previously visible threads move below the visible window and disappear from the sidebar.

I also observed a path normalization signal similar to other reports:

Some threads.cwd values use plain C:\...
Some threads.cwd values use \\?\C:\...

Normalizing or updating local metadata is not a reliable repair. Direct edits to state_5.sqlite and session_index.jsonl can change ordering/names temporarily, but the app may rewrite state after startup. Creating fresh cloned threads makes those threads appear, which suggests the stored conversations are valid; however, this only shifts which subset is visible.

What steps can reproduce the bug?

I do not have a minimal clean repro from a fresh installation, but the observed repro on this machine is:

  1. Use Codex Desktop on Windows across several local project roots.
  2. Accumulate many local threads in project-organized sidebar mode.
  3. Fully exit and restart Codex Desktop.
  4. Open the left sidebar in project mode.
  5. Observe that each project shows only a subset of its unarchived local threads.
  6. Inspect local state:
    • state_5.sqlite contains more unarchived threads than the sidebar shows.
    • session_index.jsonl contains the missing thread IDs/names.
    • rollout JSONL files exist under %USERPROFILE%\.codex\sessions.
  7. Make one hidden thread recent by cloning/restoring it as a fresh local thread.
  8. Observe that the restored/recent thread appears near the top, but another thread is pushed below the visible project window and becomes inaccessible from the sidebar.

This makes the sidebar look like it is showing a capped or filtered subset rather than enumerating all local unarchived threads.

What is the expected behavior?

Codex Desktop should surface all unarchived local threads for each project, or provide a reliable way to load/show the full project thread list.

Specifically:

  • all unarchived local threads present in state_5.sqlite and backed by rollout files should remain visible or searchable;
  • project sidebar sections should not silently cap the visible list without a way to access older threads;
  • Show more / Show less should not leave valid project threads inaccessible;
  • restarting the app should not change which valid local threads are reachable;
  • path normalization differences such as C:\... vs \\?\C:\... should not cause local threads to disappear from the project list.

Additional information

This appears closely related to several existing issues:

Compared with #17540, this report adds one concrete signal: making/cloning older hidden threads recent causes them to appear, but other valid threads are pushed out of the visible project section. That makes the failure look like a project sidebar list cap/window/filtering issue rather than corrupted individual sessions.

No local chat data appears to be deleted on this machine; the problem is that many valid local threads are not reachable through the Codex Desktop sidebar.

extent analysis

TL;DR

The issue is likely due to a sidebar enumeration/rendering bug in Codex Desktop, causing a limited number of local threads to be displayed per project.

Guidance

  • Verify that the issue is not related to data corruption by checking the state_5.sqlite and session_index.jsonl files for consistency.
  • Try cloning or restoring older hidden threads to see if they appear near the top of the project list, and if other threads are pushed out of the visible window.
  • Check if the path normalization signal (C:\... vs \\?\C:\...) is contributing to the issue by normalizing the paths and observing if the behavior changes.
  • Investigate if the issue is related to the session_index.jsonl file, as mentioned in related issues, and try updating or repairing it.

Example

No code snippet is provided as the issue seems to be related to the Codex Desktop application's behavior rather than a specific code snippet.

Notes

The issue appears to be closely related to several existing issues, and the provided information suggests that the problem is not with data loss, but rather with the application's ability to display all local threads. The path normalization signal and the behavior of cloning or restoring older threads may be contributing factors.

Recommendation

Apply a workaround by cloning or restoring older hidden threads to make them appear near the top of the project list, and consider reporting the issue to the Codex Desktop developers for further investigation and resolution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Windows Codex Desktop sidebar hides valid local project threads while SQLite and rollout files are intact [2 comments, 2 participants]