Codex Windows desktop app freezes when Goal contains raw LaTeX backslashes

Component

Codex Windows desktop app. This is not a CLI-only issue and not a Codex web issue. The CLI version below is included only as a diagnostic from the same machine.

CLI available on the same machine reports codex-cli 0.137.0. Desktop app package version was not available from the local shell.

Environment

• OS: Windows 10 Pro
• Locale/UI observed: Slovak
• Surface: Codex Windows desktop app, existing local thread

Summary

When setting/editing a Goal (Cieľ) in the Codex desktop app and pasting raw LaTeX formulas containing backslashes, the app can freeze/hang. The screenshot captured by the user shows the freeze happening while the Goal input contains multiline mathematical text with an open display math delimiter \[ and LaTeX commands such as \mathfrak, \Re, and \eta.

Reproduction

1. Open the Codex desktop app on Windows.
2. Open an existing thread.
3. Click the Goal / Cieľ control in the composer.
4. Paste a multiline goal containing raw LaTeX, for example:

Uzavriet uzku hlavnu vetu
Presne formulovat narrow shifted-d_z theorem bez finite-weight rozsirenia.
Vystup ma byt cisty retazec:
\[
S_n(h;z,w)
=
q^n Z_n(z)Z_n(w)\mathfrak S_q^d(h;z,w)
+
O_K(q^n n^{\Re z+\Re w-2-\eta}).

1. The desktop app becomes unresponsive/freezes. In the screenshot, the freeze occurs before the closing \] is visible, so an unmatched display math delimiter may be part of the trigger. It is not yet clear whether a matched formula also reproduces the hang.

Expected behavior

The Goal field should accept the text as plain text, or show a validation/rendering error, without freezing the whole desktop app.

Actual behavior

The Windows desktop app freezes/hangs while the Goal input contains raw LaTeX/backslash sequences.

Notes / likely area

This looks like a Goal-input live preview/parser/rendering issue in the desktop UI. Possible triggers are:

• raw backslashes in the Goal field;
• display math delimiter \[;
• unclosed or partially typed LaTeX during live parsing;
• expensive Markdown/LaTeX rendering running synchronously on the UI thread.

A robust fix would likely treat Goal text as plain text, or isolate/debounce math rendering and make unmatched delimiters/parser failures non-blocking.