openai / openai/codex

Deleted conversations remain in sidebar and cannot be removed or archived – HTTP 404 conversation_deleted

Open
#44,343 7 comments 1 reaction 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)?

26.903.61454 (build 8378)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

Some ChatGPT conversations remain visible in the sidebar even though the server considers them already deleted. They cannot be deleted again or archived.

Steps to reproduce:

  1. Open the ChatGPT desktop app on macOS.
  2. Open the three-dot menu next to one of the affected conversations.
  3. Select Delete or Archive.
  4. The application reports that the conversation cannot be deleted, and the entry remains in the sidebar.

Actual result:
The delete request returns HTTP 404 with the error code conversation_deleted. The server response states that the conversation has already been deleted, but its entry remains visible in the desktop application's sidebar. Archiving the same conversation also fails.

Expected result:
A conversation that has already been deleted on the server should disappear from the sidebar. I should also be able to manually delete or archive other conversations normally.

Additional information:

  • Only some conversations can be deleted.
  • The affected conversations are not visible in the ChatGPT web version.
  • The affected conversations are not actually running, although some may appear to be working in the desktop interface.
  • Reinstalling the application did not resolve the issue.
  • Completely resetting the local application profile and caches did not resolve the issue.
  • The problem persists after restarting the application.
  • The issue appears to be caused by a stale or inconsistent conversation index associated with my account.

Relevant log result:
HTTP status: 404
Error code: conversation_deleted
Request method: DELETE
Route: /conversation/id/{conversation_id}

Previous diagnostic session ID:
01a0624e-c8fc-79c3-9278-25cabf70ab64

What steps can reproduce the bug?
  1. Open the ChatGPT desktop app on macOS.
  2. Locate one of the affected conversations in the sidebar.
  3. Click the three-dot menu next to the conversation.
  4. Select Delete and confirm the deletion.
  5. The application displays an error and the conversation remains visible.
  6. Try to archive the same conversation. Archiving also fails.
  7. Restart the application. The conversation is still present.
  8. Repeat the procedure after reinstalling the application and resetting the local application profile and caches. The problem remains.

The DELETE request returns HTTP 404 with the error code conversation_deleted.

Diagnostic session ID:
01a0624e-c8fc-79c3-9278-25cabf70ab64

What is the expected behavior?

After I confirm deletion, the conversation should be permanently removed from the sidebar. If the server already considers the conversation deleted, the desktop application should remove its stale sidebar entry automatically.

Archiving should move an existing conversation to Archived Chats without displaying an error. The conversation list should remain consistent after restarting the application and across the desktop and web versions.

Additional information

Environment:

  • ChatGPT desktop app version: 26.903.61454 (build 8378)
  • Subscription: ChatGPT Plus
  • Operating system: macOS 15.8 (build 24H22)
  • Platform: Apple Silicon / arm64
  • Kernel information: Darwin 24.6.0 arm64 arm

Scope of the problem:

  • Only some conversations are affected.
  • The affected conversations are visible in the macOS desktop app but are not visible in the ChatGPT web version.
  • The affected conversations are not actually running, although the desktop interface may display a stale working state.
  • Other conversations can still be deleted normally.

Troubleshooting already completed:

  • Restarted the application.
  • Reinstalled the application.
  • Reset the local application profile.
  • Cleared the application caches.
  • The issue persists after all of these steps.

Sanitized log information:

  • Request method: DELETE
  • Route: /conversation/id/{conversation_id}
  • HTTP status: 404
  • Error code: conversation_deleted
  • The server reports that the conversation has already been deleted, but the desktop application continues to display it.

This appears to be an account-level conversation index or synchronization inconsistency rather than an active-task or local-cache problem.

Previous diagnostic session ID:
01a0624e-c8fc-79c3-9278-25cabf70ab64

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 files or tests are identified in the report. Start by tracing the DELETE /conversation/id/{conversation_id} flow and handling for the conversation_deleted 404, then inspect how the desktop sidebar refreshes after deletion or archive requests. Done means server-deleted conversations disappear from the sidebar and valid archive or delete actions remain usable after restart.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.