Conversation-state guide
Codex Thread and Queue Errors
Choose the right Codex fix for queued follow-ups, side-chat forks, thread history, SQLite startup, and app-server state failures.
Match the complete nested error, client surface, operating system, and version. Similar outer messages can hide different failures.
Safety boundary: preserve affected threads and copy unsent text before retrying; do not delete conversation databases or rollout files as a generic repair.
Choose by stage
Queued input and side-chat failures
Use these when an instruction is queued, edited, cancelled, steered, or meant for a separate side conversation.
App-server queued follow-up no longer exists
App-server queued follow-up no longer existsRecover from the Codex Desktop app-server queued follow-up error after editing, cancelling, or resending a queued message.
Open exact fix →thread history projection expected ordinal N, got N-1
thread-store internal error: thread history projection ... expected ordinal 192591, got 192590 (code -32603)Recover safely when a long Codex thread cannot fork or resume because its thread-history projection ordinal is out of sync.
Open exact fix →Choose by stage
Thread storage and startup state
Use these when a stored conversation, projection, or local database prevents startup or resume.
Codex Desktop SQLite pool times out during startup
Codex cannot access its local databaseRecover Codex Desktop when logs_2.sqlite grows large and startup fails with pool timed out while waiting for an open connection.
Open exact fix →Codex app-server initialize handshake times out in WSL mode
Codex app-server initialize handshake timed outDiagnose Codex Desktop WSL startup when the app-server initialize handshake times out and nested logs show bwrap relocation ENOENT.
Open exact fix →Choose by stage
Account and renderer state
Use these when the app reaches its backend but cannot finish account discovery or expose the expected UI state.
account/read failed during TUI bootstrap
Error: account/read failed during TUI bootstrapDiagnose Codex CLI account/read startup failures by the nested error instead of treating every case as a login problem.
Open exact fix →Codex Browser fails because browser-client is not trusted
privileged native pipe bridge is not available; browser-client is not trustedDiagnose Codex Browser plugin failures caused by a missing native pipe trust bridge or a browser-client path outside configured trusted code paths.
Open exact fix →