openai / openai/codex

Codex desktop app for Windows: recent conversation history repeatedly missing after reopening

Open
#44,445 2 comments 0 reactions 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

This issue occurs in the Codex desktop application for Windows, not in the ChatGPT website or the Codex CLI.

For at least four consecutive mornings, reopening the Codex desktop app and returning to the same conversation shows outdated history from approximately four days earlier. Recent messages are not displayed, although read-only checks confirm that those messages exist in the local conversation transcript.

Affected thread:
01a05e3e-8f1c-7082-b9ed-e413bb2a85da
Title: Proveri reference za BAPI draft

Read-only diagnostics on September 10, 2026 confirmed:

  • Reading the thread through the app's read_thread tool returned September 6 turns as the newest available history.
  • The local JSONL transcript contains both user and assistant messages from September 9–10, including the latest conversation.
  • The transcript was approximately 1.42 GB. This is an observation, not a confirmed cause.
  • No transcript files were modified or deleted during these checks.

Expected: reopening the conversation displays its latest saved messages.
Actual: the visible history repeatedly appears several days out of date.

Please investigate conversation-history loading and the discrepancy between the local transcript and the history returned by the app. Please preserve the existing conversation data. We have not established whether other users are affected.

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 reproducing the reopening behavior for the affected thread and compare the app's read_thread result with the local JSONL transcript, using the read-only diagnostics described in the issue. Done means identifying why saved September 9–10 messages are not shown and confirming that reopening displays the latest history without modifying or deleting transcript data.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
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.