Pinned conversations disappear after restarting Codex and temporarily reappear when pinning another chat
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
No source files, tests, or entry points are named. Reproduce the Windows desktop behavior across restarts, then trace startup loading and refresh behavior for the pinned-conversation sidebar state; done means all existing pinned conversations remain visible after reopening without pinning another chat.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.730.61639
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Previously pinned conversations disappear from the left sidebar in the Codex Windows desktop app after closing and reopening the application.
The conversations do not appear to be deleted. I discovered that pinning any other currently visible conversation immediately makes the previously missing pinned conversations reappear in the sidebar.
However, this restoration is only temporary. If I close Codex and open it again, the older pinned conversations disappear from the sidebar again.
This suggests that the pinned-conversation list or sidebar state is not being correctly loaded when the application starts. Performing a new pin action appears to force the sidebar or pinned-thread state to refresh, causing the missing pinned conversations to become visible again.
No error message is displayed.
I have attached a screen recording showing the behavior.
What steps can reproduce the bug?
- Open the Codex desktop application on Windows.
- Have multiple conversations pinned in the left sidebar.
- Close the Codex application completely.
- Reopen Codex.
- Observe that some previously pinned conversations are missing from the left sidebar.
- Select any currently visible conversation.
- Use the conversation menu and choose Pin chat.
- Observe that the previously missing pinned conversations immediately reappear in the left sidebar.
- Close Codex completely again.
- Reopen Codex.
- Observe that the same older pinned conversations have disappeared again.
This behavior is reproducible on my installation.
The attached video shows:
- The older pinned conversations initially missing.
- A different conversation being pinned.
- The missing pinned conversations immediately reappearing.
- The issue returning after restarting Codex.
No code snippet, token limit, or context-window condition appears to be required to trigger this bug. It appears to be related specifically to persistence or hydration of the pinned conversation state in the desktop application's sidebar.
What is the expected behavior?
All pinned conversations should remain visible in the left sidebar after closing and reopening Codex.
The pinned-conversation list should be loaded correctly when Codex starts, without requiring the user to pin another conversation to force the sidebar to refresh.
Additional information
- The affected conversations are not intentionally unpinned or archived.
- The conversations appear to still exist because they return immediately when another conversation is pinned.
- Pinning a new conversation seems to force a refresh or recalculation of the pinned-conversation list.
- The restored conversations disappear again after the application is closed and reopened.
- I have attached a video demonstrating the complete reproduction process.
- Approximate occurrence time: August 6, 2026, around 3:00 PM, UTC-3.
- Platform: Codex desktop application on Windows.
- No visible error message is produced.
App: ChatGPT desktop, powered by Codex & OWL
Version: 26.730.61639
Release date: August 4, 2026
- 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 ·