codex - 💡(How to fix) Fix Lost my pinned threads (and multiple chat threads) with latest app update. [1 participants]

Official PRs (…)
ON THIS PAGE

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#17253Fetched 2026-04-10 03:43:21
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

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

Version 26.406.31014 (1395)

What subscription do you have?

Pro

What platform is your computer?

26.3.1 (a) (25D771280a)

What issue are you seeing?

Seems i have lost my ~6 pinned threads, as well as multiple of my in-project threads (seems to be overtaken with cloud threads, or at least those are still preserved)

*unable to submit with logs/feedback ID as /feedback doesn't provide confirmation of submission after clicking 'submit'.

<img width="620" height="625" alt="Image" src="https://github.com/user-attachments/assets/199fe151-6107-411c-8d8d-5a076ca3cc4c" />

What steps can reproduce the bug?

Remains missing after restarting the app.

What is the expected behavior?

Full thread and pin continuity across restarts and app updates.

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by checking the app's data storage or synchronization settings to ensure that local threads are being properly preserved and synced with cloud threads.

Guidance

  • Verify that the app is configured to sync local threads with cloud threads, and check if there are any settings that may be causing local threads to be overwritten or deleted.
  • Check the app's data storage location to see if the pinned threads and in-project threads are still present, but not being displayed due to a synchronization issue.
  • Try resetting the app's synchronization settings or re-linking the cloud account to see if this resolves the issue.
  • If the issue persists, try submitting a new feedback report with logs to help the developers diagnose the problem, using an alternative method if the in-app submission is not working.

Notes

The issue seems to be related to data synchronization between local and cloud threads, but without more information about the app's internal workings, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try resetting the app's synchronization settings or re-linking the cloud account to see if this resolves the issue, as this may help to re-establish the connection between local and cloud threads.

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