Codex desktop: GPT-6 stuck on Thinking; sessions, screenshots, and conversation content reported missing

What version of the Codex App are you using (From “About Codex” dialog)?

Unknown; the desktop version has not been verified.

What subscription do you have?

Unknown; not collected for this report.

What platform is your computer?

macOS.

What issue are you seeing?

Reporting at the user's explicit request. During use of GPT-6 in the Codex desktop app, the user reports recurring reliability problems:

• The app frequently remains at “思考中” (“Thinking”) with no visible progress.
• Sessions are reported as lost.
• Previously supplied screenshots are reported as missing.
• Substantial portions of previous conversations are also reported as missing, breaking continuity of ongoing work.

The user's descriptions:

一直 思考中 还会丢失session

我刚刚给你那么多截图都丢了

很多对话内容都会丢。。。。

Impact: interrupted work and loss of access to previously provided context and evidence. The user requests prioritizing reliability and session/history recovery.

What steps can reproduce the bug?

User-reported workflow, not an independently reproduced minimal test:

1. Use GPT-6 in the Codex desktop app for an ongoing conversation.
2. Exchange messages and provide screenshots.
3. The user reports frequent stalls at “Thinking” and later missing sessions, screenshots, and conversation content.

Exact triggering conditions, duration of each stall, and whether the missing-content symptoms always follow a stall have not been established. There is no verified comparison with other models.

What is the expected behavior?

Requests should complete or present a clear recoverable error. Sessions, messages, and uploaded screenshots should remain available across continued use and recovery from failures. If context or attachments cannot be loaded, the app should explain what is unavailable and provide a recovery path.

Additional information

Reported on 2026-09-09.

Evidence boundary: in the reporting assistant's current conversation context, the earlier screenshot attachments are unavailable, while the user's text reports remain visible. This does not establish permanent deletion from disk or the backend. No root cause has been confirmed; persistence, history loading, attachment delivery, and model-context assembly need to be distinguished.

No diagnostic logs or screenshots are attached because they have not been retrieved and verified. No in-app feedback upload ID is available.

A search found potentially related but unconfirmed reports:

• #40342: incomplete paginated thread history despite durable transcript records.
• #43468: completed content missing from cross-task read results.

This report does not claim either issue is the cause of the user's symptoms.

No files, tests, entry points, diagnostic logs, or verified app version are identified. Start by verifying the Codex desktop version and collecting logs while reproducing the Thinking stall, session loss, and missing attachments separately. Done means establishing a reproducible failure and identifying whether persistence, history loading, attachment delivery, or context assembly is responsible.