codex - 💡(How to fix) Fix Two historical commandExecution.cwd values decode as invalid Windows drive-relative path [1 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#19567Fetched 2026-04-26 05:14:50
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
labeled ×5unlabeled ×1

Error Message

codex resume 019cd475-5fc3-7511-b835-17231deec7ba but getting Use current directory (C:\Windows\System32)Error: Failed to resume session from C:

Root Cause

Root cause isolated: this is a Codex 0.125.0 resume decoder bug, not a gpt-5.5 migration issue. Two historical commandExecution.cwd values decode as invalid Windows drive-relative paths: D:Test-..., so 0.125.0 rejects the whole resume payload as AbsolutePathBuf.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.125.0

What subscription do you have?

enteprise

Which model were you using?

gpt-5.5

What platform is your computer?

Windows:

What terminal emulator and version are you using (if applicable)?

PowerShell

What issue are you seeing?

Root cause isolated: this is a Codex 0.125.0 resume decoder bug, not a gpt-5.5 migration issue. Two historical commandExecution.cwd values decode as invalid Windows drive-relative paths: D:Test-..., so 0.125.0 rejects the whole resume payload as AbsolutePathBuf.

What steps can reproduce the bug?

codex resume 019cd475-5fc3-7511-b835-17231deec7ba but getting Use current directory (C:\Windows\System32)Error: Failed to resume session from C: \Users\admin.codex\sessions\2026\03\09\rollout-2026-03-09T22-16-27-019cd475-5fc3-7511-b835-17231deec7ba.jsonl

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by updating the commandExecution.cwd values to use absolute paths instead of drive-relative paths.

Guidance

  • The root cause of the issue is a bug in Codex CLI version 0.125.0, which rejects the resume payload due to invalid Windows drive-relative paths.
  • To verify the issue, try running the codex resume command with a different session ID or a manually corrected commandExecution.cwd value.
  • To mitigate the issue, update the commandExecution.cwd values in the resume payload to use absolute paths, such as C:\Test\... instead of D:Test-....
  • Consider checking the Codex CLI documentation for any updates or patches related to this bug.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The provided information suggests that this issue is specific to Codex CLI version 0.125.0 and Windows platform. The solution may not apply to other versions or platforms.

Recommendation

Apply workaround: update the commandExecution.cwd values to use absolute paths, as this is a known bug in the current version of Codex CLI.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Two historical commandExecution.cwd values decode as invalid Windows drive-relative path [1 participants]