macOS migration to new ChatGPT desktop app leaves Codex Projects empty despite intact local threads

Open 💬 3 comments Opened Jul 13, 2026 by omning1

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

26.707.51957

What subscription do you have?

PLus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

After updating the standalone Codex desktop app to the new combined ChatGPT desktop app on macOS, the Codex Projects view became completely empty.

The local Codex data appears to have survived the update, but the new app does not display the existing projects or threads.

Installed ChatGPT desktop version:

26.707.51957

I have confirmed the following without modifying the live data:

  • The local Codex state database still contains 7 thread records.
  • All 7 records retain their thread IDs, titles, working directories, and rollout paths.
  • Every rollout path points to an existing readable JSONL session file.
  • The session files contain valid session metadata and conversation events.
  • The largest session file is approximately 792 MB and ends with a normal task completion event.
  • The global state file still contains the saved workspace roots.
  • The saved workspace roots correspond to the working directories recorded in the thread database.
  • None of the threads are marked archived.
  • The new ChatGPT desktop app still shows an empty Projects view.

I created a complete backup before doing any additional troubleshooting. I have not deleted application data, edited the SQLite database, removed the Codex directory, or reinstalled the app.

Steps to reproduce

  1. Use the standalone Codex desktop app on macOS with multiple local projects and existing threads.
  2. Accept the update that migrates the standalone Codex app to the new combined ChatGPT desktop app.
  3. Open the Codex Projects view in the new app.
  4. The Projects view is empty even though the existing thread database, workspace metadata, and JSONL session files remain on disk.

Expected behavior

Existing Codex projects and threads should remain visible and usable after updating to the new ChatGPT desktop app.

Actual behavior

The Projects view is empty. Existing threads remain present locally but cannot be accessed through the app interface.

Additional technical details

The local thread table contains the same number of records as the number of session JSONL files. Each database record points to its corresponding existing rollout file.

The global state still includes:

  • electron-saved-workspace-roots
  • active-workspace-roots
  • project-order

The saved workspace roots are populated rather than empty.

I can provide sanitized schema information or diagnostic output privately if needed, but I do not want to publicly post project names, local filesystem paths, source code, conversation contents, authentication files, or the session archives.

What steps can reproduce the bug?

  1. Use the standalone Codex desktop app on macOS with multiple local projects and existing threads.
  2. Accept the update that migrates the standalone Codex app to the new combined ChatGPT desktop app.
  3. Open the Codex Projects view in the new app.
  4. The Projects view is empty even though the existing thread database, workspace metadata, and JSONL session files remain on disk.

What is the expected behavior?

Existing Codex projects and threads should remain visible and usable after updating to the new ChatGPT desktop app.

Additional information

The local thread table contains the same number of records as the number of session JSONL files. Each database record points to its corresponding existing rollout file.

The global state still includes:

  • electron-saved-workspace-roots
  • active-workspace-roots
  • project-order

The saved workspace roots are populated rather than empty.

I can provide sanitized schema information or diagnostic output privately if needed, but I do not want to publicly post project names, local filesystem paths, source code, conversation contents, authentication files, or the session archives.

View original on GitHub ↗

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