Codex Desktop crashes conversation renderer when Git directive contains Windows cwd path
What version of the Codex App are you using (From “About Codex” dialog)?
Codex App version: 26.513.3673.0
What subscription do you have?
Subscription: Pro
What platform is your computer?
Platform: Windows
What issue are you seeing?
After updating Codex Desktop, conversations can crash with “앗, 오류가 발생했습니다” when a Git directive contains a Windows-style cwd path.
The issue appears when the final assistant message includes directives like:
::git-stage{cwd="D:\CodeAnvil"}
::git-commit{cwd="D:\CodeAnvil"}
::git-push{cwd="D:\CodeAnvil" branch="main"}
The conversation view then fails to render. The app log shows:
invalid syntax at line 1 col 5:
1 cwd="D:\CodeAnvil"
^
If I archive the affected conversation, other conversations become visible again. Disabling the Git plugin also appears to avoid the issue.
What steps can reproduce the bug?
- Use Codex Desktop on Windows.
- Enable the Git plugin.
- Work in a repository located at a Windows path, for example:
D:\CodeAnvil
- Have Codex complete a Git operation such as staging, committing, and pushing.
- Let the final assistant response include Git directives with a Windows-style cwd path, for example:
::git-stage{cwd="D:\CodeAnvil"}
::git-commit{cwd="D:\CodeAnvil"}
::git-push{cwd="D:\CodeAnvil" branch="main"}
- Open or return to that conversation.
- The conversation renderer crashes and shows:
“앗, 오류가 발생했습니다”
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
same
<img width="954" height="475" alt="Image" src="https://github.com/user-attachments/assets/57640527-7f11-4bc5-abcc-affda2dab6e7" />
Temporary workaround for Windows users until Codex ships a fix.
The issue seems to be caused by Codex Desktop re-parsing old local JSONL session messages that contain directive-like blocks with Windows paths, for example
cwd="D:\project\repo". The thread data is still there, but the Desktop renderer crashes while rendering the history.This PowerShell one-liner does a narrow local repair:
%USERPROFILE%\.codex\sessionsand%USERPROFILE%\.codex\archived_sessions.bak-pathfix-<timestamp>backups before editingcwd,cwds, orfileD:\foo\bartoD:/foo/bar_Run from PowerShell:_
We've issued a hotfix to address this. Please update to the latest version.