Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop: archived local thread cannot be resumed after restore due to mismatched path between sessions/ and archived_sessions/ [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20317•Fetched 2026-05-01 05:44:03
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
davyleeedavyleee
Participants
davyleeedavyleeegithub-actions[bot]github-actions[bot]scottbarbag-uxscottbarbag-ux
Timeline (top)
cross-referenced ×3labeled ×3commented ×2

Error Message

The UI repeatedly shows this error: thread/read appears to succeed, but thread/resume fails immediately with JSON-RPC error -32600 4. Codex shows a restore failure dialog with a mismatched path error.

Code Example

cannot resume running thread 019ddc40-fd28-7ca3-b05a-5de11ca24124 with mismatched path:
requested `/Users/sprite/.codex/sessions/2026/04/30/rollout-2026-04-30T10-38-59-019ddc40-fd28-7ca3-b05a-5de11ca24124.jsonl`,
active `/Users/sprite/.codex/archived_sessions/rollout-2026-04-30T10-38-59-019ddc40-fd28-7ca3-b05a-5de11ca24124.jsonl`
RAW_BUFFERClick to expand / collapse

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

26.422.71525

What subscription do you have?

Enterprise

What platform is your computer?

macOS 26.4.1 arm64

What issue are you seeing?

A local Codex Desktop thread became unrecoverable after being archived and then restored / reopened.

The UI repeatedly shows this error:

cannot resume running thread 019ddc40-fd28-7ca3-b05a-5de11ca24124 with mismatched path:
requested `/Users/sprite/.codex/sessions/2026/04/30/rollout-2026-04-30T10-38-59-019ddc40-fd28-7ca3-b05a-5de11ca24124.jsonl`,
active `/Users/sprite/.codex/archived_sessions/rollout-2026-04-30T10-38-59-019ddc40-fd28-7ca3-b05a-5de11ca24124.jsonl`

Important detail: local state is already back to the non-archived path, but thread/resume still believes the active rollout lives under archived_sessions/.

Environment: Codex Desktop App version: 26.422.71525 Bundled session metadata cli_version: 0.126.0-alpha.8 Platform: macOS 26.4.1 arm64 Additional evidence:

The session file now exists only under ~/.codex/sessions/... The row in ~/.codex/state_5.sqlite is already archived=0 and points to sessions/... Restarting Codex does not fix the mismatch thread/read appears to succeed, but thread/resume fails immediately with JSON-RPC error -32600 This looks like a desktop archive/restore state mismatch between the indexed thread path and a separate active rollout path used by resume.

What steps can reproduce the bug?

I do not yet have a fully minimal repro, but this is the sequence that produced the issue:

1. Create and use a normal local desktop thread.
2. Archive that thread from the Codex Desktop UI.
3. Later try to restore / reopen / resume the archived thread from the UI.
4. Codex shows a restore failure dialog with a `mismatched path` error.
5. Fully quit and relaunch Codex.
6. Retry opening the same thread.
7. The same resume failure still occurs.

Observed local state after the failure:

1. The session JSONL exists only at:
   `~/.codex/sessions/2026/04/30/rollout-2026-04-30T10-38-59-019ddc40-fd28-7ca3-b05a-5de11ca24124.jsonl`
2. There is no matching session JSONL left under:
   `~/.codex/archived_sessions/`
3. The row in `~/.codex/state_5.sqlite` for thread `019ddc40-fd28-7ca3-b05a-5de11ca24124` is already non-archived and points to `sessions/...`
4. Despite that, the desktop app still reports that the active rollout path is `archived_sessions/...`

Thread id:
`019ddc40-fd28-7ca3-b05a-5de11ca24124`

### What is the expected behavior?

_No response_

### Additional information

_No response_

extent analysis

TL;DR

The issue can likely be resolved by manually updating the active rollout path in the Codex Desktop App to match the non-archived path.

Guidance

  • Verify that the session JSONL file exists only in the ~/.codex/sessions/ directory and not in ~/.codex/archived_sessions/.
  • Check the ~/.codex/state_5.sqlite database to ensure the row for the thread 019ddc40-fd28-7ca3-b05a-5de11ca24124 is marked as non-archived and points to the correct path in sessions/.
  • Attempt to manually update the active rollout path used by the resume function to match the non-archived path.
  • If the issue persists, try deleting the archived session entry from the ~/.codex/state_5.sqlite database and restarting the Codex Desktop App.

Notes

The provided information suggests a state mismatch between the indexed thread path and the active rollout path used by the resume function. However, without direct access to the Codex Desktop App's code or further documentation, the exact steps to resolve the issue may vary.

Recommendation

Apply a workaround by manually updating the active rollout path to match the non-archived path, as this appears to be the root cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING