[Linux desktop] Deleted ChatGPT conversations persist as undeletable ghost entries in sidebar; local catalog rows survive profile reset #47517

Environment

• ChatGPT desktop app on Linux (Omarchy, Wayland), executable /usr/lib/chatgpt/ChatGPT.
• App data under ~/.config/Codex; local thread index at ~/.codex/sqlite/codex-dev.db.
• App version/build: not yet collected.

Problem

Recurring ghost ChatGPT conversation titles remain in the Linux desktop app's sidebar every few weeks. Opening one says the conversation is no longer available. These entries are absent from chatgpt.com and other devices. The user cannot remove the stale entries through the normal desktop UI.

Tried without success

• Sign out and back in; completely close/restart the desktop app.
• Clear Chromium Cache, Code Cache and GPUCache.
• Move ~/.config/Codex/Default aside to force a fresh browser profile.

Confirmed local cause / workaround

The ghost conversation existed in ~/.codex/sqlite/codex-dev.db, table local_thread_catalog, with source_kind='chatgpt' and missing_candidate=0. Other older entries had missing_candidate=1 but were not visible ghosts, so that flag does not reliably identify sidebar ghosts. With the application fully closed and the complete sqlite directory backed up (including WAL/SHM), deleting ONLY the rows matching five individually verified ghost titles from local_thread_catalog removed those sidebar entries on restart. This operation did not request deletion of any server-side conversation.

Expected

The desktop sidebar should reconcile its local catalog with available ChatGPT conversations and automatically remove entries whose source conversations no longer exist. Attempts to remove a missing chat should succeed locally rather than requiring manual SQLite modification. Ideally offer a safe refresh/rebuild sidebar index action preserving genuine chats, local Work sessions, and other app state.

Impact

This is recurrent and requires the user to close the app and edit an internal SQLite database to restore a usable sidebar. The user reports they may stop using the app if the issue keeps recurring.

Related reports: #42628, #41987, #41399. This report adds a verified Linux/Omarchy reproduction and an individually confirmed local-catalog workaround. Please merge or cross-reference if appropriate.