Codex Desktop 26.616 loses Project conversation after HTTP 429 despite rollout being fully persisted

Open 💬 1 comment Opened Jun 27, 2026 by killa0132

Path:

OS:
Windows 11

Codex:
26.616.81150

Login:
API Key

Workspace:

Initially:
C:\Users\Nijika\Documents\ColorAssistance

Later migrated to

D:\ColorAssistance

Model:
GPT-5.5 / Codex

Reproduction steps:

1.
Create a Project.

2.
Work continuously for 10+ rounds.

Approximately 630 rollout events.

3.
Generate many files.

4.
Ask Codex to migrate the workspace from C: to D:.

5.
Click "New Chat".

6.
Immediately receive

429 Too Many Requests

7.
Restart Codex.

8.
Project sidebar now shows

"No conversations"

although all project files remain.

Actual result:

Conversation disappears from sidebar.

Project remains.

Workspace remains.

Rollout exists.

No session entry exists.

Cannot continue the conversation.

Expected result:

429 should not remove or orphan an existing Project conversation.

If rollout has been persisted,

the conversation should remain visible or recoverable.

Confirmed data:

✓ rollout exists

630 events

75 user messages

71 assistant messages

✓ project files intact

✓ sqlite contains related records

✗ session_index.jsonl

does not contain

019eff78

✗ global state

does not contain

019eff78

Result:

Conversation cannot be reconstructed by the UI despite rollout existing.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗