[Windows][Desktop 26.831.2377.0] Thread history projection stuck after Remote Control session: expected ordinal 6758, got 6757

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

26.831.2377.0

What subscription do you have?

plus

What platform is your computer?

No response

What issue are you seeing?

Summary

Codex Desktop no longer displays recent conversation history after a long Remote Control session.

The conversation data is not lost. Original rollout files and SQLite databases remain intact, but the local history projection stops updating.

Environment

Codex Desktop:
26.831.2377.0

Codex CLI:
0.152.1

OS:
Windows

Affected thread

Thread ID:

01a04e60-2d7e-79a2-8287-395d52a09886

Symptoms

After restarting Codex:

• Project/workspace restored
• Old conversations visible
• Newer conversations missing from sidebar history

The active conversation data still exists locally.

Diagnostics

SQLite integrity:

PASS

Databases:

• state_5.sqlite
• thread_history_1.sqlite
• logs_2.sqlite

All integrity checks return OK.

Rollout files:

Present and continue updating.

Error

Repeated log:

expected ordinal 6758, got 6757

First observed:

2026-08-31 08:00:45

Still occurring:

2026-09-02

Migration state

projectsMigrated=true

threadAssignmentsMigrated=false

Additional findings

migrate-rollouts dry-run:

status = already_paginated

The affected thread is already paginated, so migrate-rollouts does not rebuild it.

Expected behavior

Codex should rebuild or recover history projection automatically after detecting an ordinal mismatch.

Actual behavior

History projection stops permanently and sidebar history remains stale.

Request

Please provide a supported way to:

• rebuild thread history projection
  or
• retry thread assignment migration
  or
• repair the projection cursor safely.

What steps can reproduce the bug?

Steps to reproduce

1. Install Codex Desktop on Windows.
2. Enable Remote Control features in Codex configuration.
3. Create or open a long-running project conversation.
4. Continue working in the same thread for multiple days with many tool executions.
5. Restart Codex Desktop.
6. Open the same project/thread from the sidebar.

Expected behavior

Codex should display the latest conversation history and continue updating the thread normally.

Actual behavior

The sidebar only shows old conversation history. Newer messages are missing from the visible history.

The conversation data is not lost:

• rollout files still exist
• SQLite databases pass integrity checks
• the active thread data continues to update

However, history projection stops updating.

Relevant error found in logs:

expected ordinal 6758, got 6757

The error repeats after restarting Codex.

Affected thread:

01a04e60-2d7e-79a2-8287-395d52a09886

Environment:

Codex Desktop: 26.831.2377.0
Codex CLI: 0.152.1
OS: Windows

What is the expected behavior?

No response

Additional information

No response

Start by tracing the migrate-rollouts path and the thread history projection using the reported ordinal mismatch, migration state, and SQLite databases as the investigation context. Reproduce or inspect the repeated error, then verify that the projection can recover and that newer conversation history appears in the sidebar without losing rollout data.