codex - 💡(How to fix) Fix Codex Desktop crashes conversation renderer when Git directive contains Windows cwd path

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…
RAW_BUFFERClick to expand / collapse

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?

  1. Use Codex Desktop on Windows.

  2. Enable the Git plugin.

  3. Work in a repository located at a Windows path, for example: D:\CodeAnvil

  4. Have Codex complete a Git operation such as staging, committing, and pushing.

  5. 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"}

  6. Open or return to that conversation.

  7. The conversation renderer crashes and shows: “앗, 오류가 발생했습니다”

What is the expected behavior?

No response

Additional information

No response

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