2 people reported

All time, since Sep 30.

Desktop UI freezes after updates when cua_node runtime cache is missing

“After updating the Windows desktop app, switching back from another application and opening existing chats repeatedly freezes the interface.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14383/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 2 a week at the late-September peak. A workaround is known.

Switching windows, opening Settings, navigating chats or typing triggers "Not responding" while runtime preparation fails with rename_staging EPERM.

Is this your bug?

File my report
Where
Windows desktop app
Error text
bundled_executable_relocation_failed
Platforms
Windows
How bad
Breaks a normal workflow. Most reports say it used to work.

Not quite your bug?

  1. Startup rename_staging EPERM5 people
  2. App launches with no window3 people

Original reports3, newest first

  1. Windows desktop freezes after updates: a verified workaround for missing cua_node runtime cachesOn GitHub Discussions#55820
  2. Windows desktop app repeatedly freezes during interaction after recent updates; rebuilding matching runtime cache restores useOn GitHub#50256
  3. [Windows] Repeated UI freezes on focus and chat switching after updates: cua_node rename_staging EPERM retry loop (26.928.2636.0)On GitHub#49611

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.