Threads keep disappearing from the sidebar even with "All chats" selected

Resolved 💬 4 comments Opened Apr 15, 2026 by abagherpour Closed Apr 15, 2026

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

Codex app 26.409.20454 (1462)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Threads keep disappearing from the sidebar even though:

  • Show -> All chats is selected
  • I am sure I did not archive those threads

The project still appears in the sidebar, but it suddenly shows No chats even though that project previously had multiple threads.

Expected behavior

If All chats is selected, existing threads should remain visible in the sidebar unless I explicitly archive them.

Actual behavior

A project that previously had threads starts showing No chats, and those threads no longer appear in the sidebar.

What I tried

I already checked the obvious sidebar options:

  • Show -> All chats
  • Organize -> By project
  • Organize -> Chronological list

Those settings do not bring the missing threads back.

Additional notes

This looks like a sidebar/indexing issue rather than intentional filtering.

I also checked locally and found that the underlying thread/session data still appears to exist, which makes this look like a UI/state bug rather than actual deletion.

I can provide

  • redacted screenshots
  • sanitized local diagnostics showing the threads still exist on disk / in the local index

What steps can reproduce the bug?

I do not have a small repro yet, but this is the pattern I keep seeing:

  1. Use Codex desktop across multiple local projects
  2. Accumulate multiple threads in a project
  3. Later open the sidebar again
  4. The project is still listed, but now shows No chats
  5. All chats is already selected, and I did not archive those threads

What is the expected behavior?

If All chats is selected, existing threads should remain visible in the sidebar unless I explicitly archive them.

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗