Historical Codex project threads missing after migration to unified ChatGPT desktop app
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
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
- Windows installed normal updates and restarted.
- The standalone Codex desktop application was replaced by the new ChatGPT desktop application.
- I was prompted to sign in again.
- Initially the Projects section showed "No projects."
- My ChatGPT cloud Projects and conversations remained available on chatgpt.com.
- 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?
-
Use the standalone Codex desktop application with one or more existing Git repository projects containing historical Codex threads.
-
Update to the new unified ChatGPT desktop application (Powered by Codex & OWL).
-
Restart Windows if prompted.
-
Launch the new ChatGPT desktop application.
-
Sign in again if prompted.
-
Observe that the Projects section reports "No projects."
-
Reattach the existing repository using:
Projects → Use an existing folder
-
Select the existing Git repository.
-
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·