openai / openai/codex

[Codex App] Long-running task history is missing and does not load on another computer

Open
#45,354 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

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

26.908.40834

What subscription do you have?

PRO

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The history of a long-running Codex task named “Tabelly + Integration Hub” is incomplete and no longer loads correctly.

The task contains more than one month of development work on QURAU and Integration Hub. The task itself is still identifiable, but a substantial part of its earlier conversation and development history is inaccessible.

The missing history is also unavailable when I sign in with the same account on another computer. Restarting and reopening the Codex app does not restore it.

I preserved local project artifacts and recovered part of the history from local files, but this is not a complete replacement for the original Codex task history.

No Codex application database was edited or reset, and I did not reinstall the app because that could destroy recoverable local state.

What steps can reproduce the bug?

Feedback ID: 019f79b2-cd8f-78e3-9b03-6b2e01c7c8bd

What is the expected behavior?

The complete task history should remain available and load consistently on the original computer and on another computer signed in to the same account.

If the history cannot be displayed because of a synchronization, indexing, or migration failure, the app should provide a clear recovery or export mechanism without requiring deletion or reset of local application data.

Additional information

The missing history represents more than one month of development work.

I previously contacted OpenAI support and supplied my contact email, but received only automated responses. No ticket number or confirmed human escalation was provided, and the history has not been restored.

I can provide sanitized diagnostics privately if needed. I cannot publish raw session databases, credentials, private source code, or complete application logs in this public GitHub issue.

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 with the reported Feedback ID 019f79b2-cd8f-78e3-9b03-6b2e01c7c8bd and the Codex App history-loading and synchronization entry points; the payload names no source files or tests. Investigate why the long-running task history is incomplete across computers, while preserving local application data. Done means the complete history loads consistently or the app provides a safe recovery or export path.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.