openai / openai/codex

Codex Desktop: historical turns unavailable although task remains visible

Open
#44,015 1 comment 0 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

Summary

A Codex Desktop task can remain visible and openable in the sidebar, while its older conversation turns are no longer available in the history view.

Observed behavior

  • The existing task remains visible in the sidebar and is not archived.
  • Opening the task shows only recent turns.
  • The history response reports no additional page/cursor, despite older turns previously existing for the task.
  • Fully restarting the desktop app does not restore the missing history.

Expected behavior

If retained historical turns exist, Codex Desktop should enumerate them or provide a clear recovery/error state. A task that remains visible should not silently expose only a recent subset of its history.

Impact

This makes long-lived tasks unreliable as working records because earlier decisions and context cannot be reviewed.

Privacy note

No conversation content, task identifiers, account details, local files, screenshots, or logs are attached to this report.

Request

Please investigate historical-turn indexing, migration, and pagination behavior in Codex Desktop, and advise whether affected histories can be recovered.

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 missing-history behavior in Codex Desktop, then inspect the historical-turn indexing, migration, and pagination paths described in the report. Done means retained turns are enumerated correctly, or the app provides a clear recovery or error state and the possibility of recovering affected histories is documented.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.