openai / openai/codex

Codex app sidebar repeatedly shows stale “ghost” conversations that no longer exist

Open
#46,349 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

Version 26.911.61220

What subscription do you have?

Plus

What platform is your computer?

MacOS, Windows

What issue are you seeing?

The Codex desktop app does not reliably synchronize deleted or archived conversations across devices.

When I delete or archive a conversation on one machine, the change is not propagated correctly to Codex on my other machines. The other machines continue to show the conversation in their sidebars as a “ghost” entry, even though it has already been deleted or archived elsewhere.

These stale entries cannot be opened or read, and attempting to delete or archive them again does not remove them. Restarting or refreshing Codex also does not reliably resolve the issue.

This is not specific to one operating system. The underlying problem appears to be that conversation deletion and archive state are not synchronized across devices, leaving stale records in each device’s local sidebar catalog.

Expected behavior: deleting or archiving a conversation on one device should synchronize to every other device signed into the same account. Deleted conversations should disappear from all sidebars, while archived conversations should move to the archived list on every device. Stale local entries should be automatically removed during synchronization.

What steps can reproduce the bug?
  1. Sign in to the same Codex account on two different machines.
  2. Create or open a conversation and confirm that it appears in the sidebar on both machines.
  3. Delete or archive the conversation on Machine A.
  4. Open or refresh Codex on Machine B.
  5. The conversation remains in Machine B’s sidebar, but it cannot be opened, read, deleted, or archived again.
What is the expected behavior?
Image
Additional information

No response

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.

Research direction

No source file or test is named. Reproduce the two-machine deletion and archive flow described in the issue, then trace how sidebar conversation state is synchronized and removed locally; done means deleted conversations disappear and archived conversations move to the archived list on every signed-in device.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.