Codex Desktop error boundary when rendering git directives with Windows cwd paths

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

Codex Desktop 26.513.31313

What subscription do you have?

Pro.

What platform is your computer?

Windows, x64

Shell: PowerShell

What issue are you seeing?

Codex Desktop shows the generic error boundary screen:

Oops, an error has occurred

The crash appears to happen while rendering a saved assistant message that contains Codex git directives with a Windows path in the cwd attribute.

Sanitized example of the triggering message content:

::git-stage{cwd="C:\path\to\repo"}
::git-commit{cwd="C:\path\to\repo"}
::git-push{cwd="C:\path\to\repo" branch="main"}

After opening or rendering the affected thread, the app displays the error boundary instead of the conversation.

What steps can reproduce the bug?

1. Use Codex Desktop on Windows.
2. Have a saved conversation/thread containing an assistant message with git directive-like lines that include a Windows backslash path in cwd, for example:

``text
::git-stage{cwd="C:\path\to\repo"}
``

1. Open or reopen that thread in Codex Desktop.
2. The thread fails to render and shows the generic error boundary screen.

What is the expected behavior?

The conversation should render normally. A saved message containing directive-like text or a Windows path should not make the whole conversation view fail to load.

What actually happens?

The entire thread fails to render and shows the generic error boundary.

Relevant sanitized log excerpt:

error [electron-message-handler] error boundary
name=LocalConversationPage
errorMessage="invalid syntax at line 1 col 5:

1  cwd=\"C:\\path\\to\\repo\"
       ^"

The component stack included Markdown/thread rendering code, including:

markdown-*.js
local-conversation-thread-*.js
local-conversation-page-*.js

Additional information

This appears to be a renderer/parsing issue rather than a repository or git failure. The affected repository and git state were normal; the failure occurred while the desktop app was rendering the saved conversation history.

I have intentionally omitted local usernames, account details, repository names, and exact filesystem paths from this report.