Historical Codex project threads missing after migration to unified ChatGPT desktop app

Open
#33,357 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
desktop-dev

Research direction

Start by reproducing the migration flow on Windows: update from the standalone Codex app, sign in, reattach an existing repository through Projects → Use an existing folder, and verify whether it reports 0 threads. Done means historical Codex threads are restored for the repository, or the unified app clearly communicates that migration is unsupported.

Written by the indexing model from the issue text.

Description

app bug session windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

26.707.72221

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?
App Version

ChatGPT Desktop (Powered by Codex & OWL)

Version:
26.707.72221

Platform:
Windows 11

Feedback ID:
no-active-thread-019f663d-c1ff-7ff2-b7e8-9d769fa235d6


Summary

After the standalone Codex desktop application was replaced by the new unified ChatGPT desktop application, my existing repositories can be reattached successfully, but all historical Codex project threads appear to be missing.


What happened
  1. Windows installed normal updates and restarted.
  2. The standalone Codex desktop application was replaced by the new ChatGPT desktop application.
  3. I was prompted to sign in again.
  4. Initially the Projects section showed "No projects."
  5. My ChatGPT cloud Projects and conversations remained available on chatgpt.com.
  6. I reattached my existing Git repositories using:

Projects → Use an existing folder

Both repositories were detected correctly.

Examples:

C:\Bespoke\bespoke-operating-system

C:\Bespoke\bespoke-automation-governance

The application correctly recognizes:

  • Git repository
  • Branch (main)
  • Local repository path

However each repository reports:

0 threads

Searching for previous work only returns ChatGPT conversations and does not return any historical Codex project threads.


Expected behavior

If historical Codex project threads are intended to migrate to the unified ChatGPT desktop application, they should remain associated with the repository after reattachment.

If migration is not currently supported, it would be helpful for the application to communicate that existing Codex project thread history will not be available after migration.


What is still working
  • ChatGPT cloud Projects are intact.
  • ChatGPT conversations are searchable.
  • Git repositories are intact.
  • Git history is intact.
  • Repository contents are intact.
  • Existing repositories can be attached successfully.

Only the historical Codex project thread history appears to be missing.


Additional notes

Windows setup completed successfully after attaching the repositories.

The issue persists after:

  • signing out and back in
  • reattaching repositories
  • completing Windows setup
What steps can reproduce the bug?
  1. Use the standalone Codex desktop application with one or more existing Git repository projects containing historical Codex threads.

  2. Update to the new unified ChatGPT desktop application (Powered by Codex & OWL).

  3. Restart Windows if prompted.

  4. Launch the new ChatGPT desktop application.

  5. Sign in again if prompted.

  6. Observe that the Projects section reports "No projects."

  7. Reattach the existing repository using:

    Projects → Use an existing folder

  8. Select the existing Git repository.

  9. Observe that:

    • The repository is detected correctly.
    • The Git branch is detected correctly.
    • The repository opens successfully.
    • The project reports "0 threads."
    • Searching only returns ChatGPT conversations and does not return historical Codex project threads.
What is the expected behavior?

No response

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.