A long-running Codex Desktop conversation became unreadable. Its local session JSONL contains large runs of literal NUL bytes and malformed records that fail standard JSON parsing.
Here's what Codex itself says about it:
read_thread returns one inProgress turn with empty items, hasMore: false, and no next cursor, despite later messages remaining in the log.- Removing NUL bytes in memory and skipping invalid records recovers readable messages, but does not restore the app's history display or guarantee complete recovery.
Expected: Valid, accessible history, with non-destructive recovery when corruption is detected.
Environment: Codex Desktop over remote SSH; session metadata reports CLI 0.155.1. Desktop build unknown.
Reproduction: Trigger unknown; no reliable reproduction steps established.
Possibly related: #24369, #25290, #44461. A shared cause is unconfirmed.
No project details, paths, session identifiers, conversation excerpts, or raw logs are included.
A long-running Codex Desktop conversation became unreadable. Its local session JSONL contains large runs of literal NUL bytes and malformed records that fail standard JSON parsing.
Here's what Codex itself says about it:
read_threadreturns oneinProgressturn with emptyitems,hasMore: false, and no next cursor, despite later messages remaining in the log.Expected: Valid, accessible history, with non-destructive recovery when corruption is detected.
Environment: Codex Desktop over remote SSH; session metadata reports CLI
0.155.1. Desktop build unknown.Reproduction: Trigger unknown; no reliable reproduction steps established.
Possibly related: #24369, #25290, #44461. A shared cause is unconfirmed.
No project details, paths, session identifiers, conversation excerpts, or raw logs are included.