openai / openai/codex

Completed local Codex responses disappear after restarting ChatGPT desktop app

Open
#40,950 4 comments 3 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

Problem

Completed responses from a local Codex agent disappear from conversations after restarting the ChatGPT desktop app.

A full response is initially visible and complete. After fully quitting and reopening the app, the conversation is truncated to the agent’s introductory message and first command/tool invocation. The subsequent tool activity and completed final response are gone.

This has now happened repeatedly, primarily in conversations associated with one local Helpdesk project. The conversations remain visible, but their contents are incomplete.

Confirmed reproduction on August 26, 2026

While preparing this issue, I deliberately tested whether the problem would recur.

  1. My local Codex agent completed a task and displayed a full final response.
  2. I copied that complete response into another ChatGPT conversation, proving it was present and visible.
  3. I closed and reopened the affected conversation/app.
  4. The completed response disappeared.
  5. Only the agent’s first partial message remained.

This reproduced the issue with newly generated content. It is not limited to an older conversation, a hidden sidebar entry, or an archived chat.

At least two separate completed local Codex responses have now disappeared this way.

Steps to reproduce

  1. Open a local Codex conversation.
  2. Submit a task and wait for the agent to finish.
  3. Confirm that the complete final response is visible.
  4. Fully quit the ChatGPT desktop app.
  5. Reopen the app and return to the conversation.
  6. Observe that the conversation is truncated to an earlier point and the completed response is missing.

Expected behavior

All completed messages, tool activity, and final responses should remain available after closing and reopening the app.

Actual behavior

The conversation reopens with later content missing. It ends after the agent’s initial response and first command, even though a complete final report had previously been displayed.

Environment

  • macOS
  • ChatGPT desktop app version: 26.819.11345
  • Local Codex workspace
  • Workspace dependency diagnostic: healthy
  • Archived Chats: empty
  • Refresh did not restore the content
  • Fully restarting the app did not restore the content
  • The “Chronological” sidebar filter described in the troubleshooting documentation is not present in this app interface

Feedback report

Feedback ID:

no-active-thread-01a03f4f-9c44-79d2-b559-db522f35723b

The feedback was submitted with “Include current ChatGPT session logs” enabled. Opening feedback from inside the affected conversation displayed the same feedback mechanism.

Additional information

This is not merely a missing sidebar entry. The affected conversation can still be opened, but previously displayed content within it has disappeared.

The completed work itself was independently copied or saved elsewhere, confirming that the missing final response genuinely existed before the app was reopened.

Image Image

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 loss from a local Codex conversation in the ChatGPT desktop app, following the listed steps and checking the submitted feedback/session logs. Trace how the conversation is saved after the final response and restored after restart. Done means completed messages, tool activity, and final responses remain available after reopening.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.