openai / openai/codex

[Windows][Desktop 26.825.6671.0] Deleted conversations persist in Recents after reset, re-login, and canonical-list removal

Open
#41,693 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of the Codex App are you using?

Microsoft Store package OpenAI.Codex 26.825.6671.0 x64.

The problem was also reproduced on 26.825.5331.0 before updating.

What platform are you using?

Windows desktop app (ChatGPT / Codex unified app), Japanese locale.

Summary

Deleted conversations continue to appear under the Windows desktop app's Recents section even though they no longer exist in the canonical ChatGPT/Codex thread lists.

Only the currently active thread should remain:

  • Fix recent items deletion bug

The following deleted entries still appear:

  • めざしの冷凍保存確認
  • 土田部長の気分推測
  • Codex App Server活用 horosuke
  • 海鮮焼き方案内

Actual behavior

The four deleted entries remain visible under 最近の項目 / Recents.

Attempts to pin, archive, open, or remove the stale entries fail or have no durable effect. One known deleted ChatGPT conversation ID returned:

No Codex thread found for threadId: <deleted-id>. Hosts without a readable match: local

Evidence

Read-only diagnostics showed:

  1. The four deleted titles are absent from the supported unified list_threads result.
  2. The canonical task section contains only the current Codex thread.
  3. The titles and the known deleted ChatGPT conversation ID are absent from %USERPROFILE%\.codex\.codex-global-state.json.
  4. ChatGPT Web does not show these four conversations in its chat history.
  5. Therefore, the stale rows appear to come from a Windows-desktop-specific Recents projection/catalog that disagrees with both ChatGPT Web and the supported thread list.

A screenshot showing the stale Recents rows is available and can be provided privately if maintainers identify a suitable diagnostic channel.

Troubleshooting already performed

  • Deleted the affected conversations through the UI.
  • Fully quit and restarted the app.
  • Restarted Windows.
  • Signed out and signed back in.
  • Used Windows Repair for the app.
  • Used Windows Reset for the app.
  • Reauthenticated after reset.
  • Updated the Store app from 26.825.5331.0 to 26.825.6671.0.
  • Cleared display/cache data.
  • Verified the supported thread list.
  • Backed up and removed only orphaned IDs without rollout/session files from .codex-global-state.json -> projectless-thread-ids.

The orphaned-ID cleanup reduced projectless-thread-ids from 16 to 2 while preserving the current thread and one legitimate archived session, but it did not remove the four stale Windows Recents rows. This indicates the visible rows are owned by another catalog/projection.

Reproduction

  1. Delete conversations shown in the Windows desktop Recents list.
  2. Confirm they disappear or become inaccessible.
  3. Fully quit/restart the desktop app, reset it, or sign out and sign back in.
  4. Observe that the deleted titles reappear under Recents.
  5. Check ChatGPT Web and the supported unified thread list.
  6. Observe that the same deleted conversations are absent there.

Expected behavior

  • A deleted conversation must not reappear in any active sidebar or Recents view.
  • The Windows desktop Recents projection should reconcile against deletion tombstones and the canonical thread list.
  • Orphaned/stale rows should have a supported "remove stale reference" operation even when the backing thread no longer exists.

Related reports

  • #41214 — archived or deleted tasks can reappear after restart.
  • #38724 — orphaned sidebar entries cannot be archived or deleted.
  • #39492 — Windows archive operations fail and block deletion.
  • #32578 — earlier orphaned-entry regression that was closed, followed by recurrence reports.

Privacy

The four visible titles are included with the user's explicit permission. No project files, prompts, account identifiers, local paths beyond generic locations, or private logs are attached.

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

Start by tracing the Windows desktop Recents projection/catalog and compare it with the supported list_threads result and deletion handling. Use the reported stale titles and the projectless-thread-ids entry in %USERPROFILE%.codex.codex-global-state.json as diagnostic references; done means deleted conversations no longer reappear after restart, reset, or re-login.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.