Codex App on Windows intermittently redirects active threads to the "New Thread" page

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #14406

Powered by Codex Action

I had a very similar experience this morning after using app successfully yesterday. Main difference in my case was that I switched to use WSL (Ubuntu) to resolve a different issue this morning. I noticed this issue ( redirects to the "Create New Thread" page) immediately after that switch. I reverted back to use Powershell and the issue is no longer present.

Same issue for me. In my case I was set to Powershell and the UI kept resetting because the Terminal panel kept throwing:

node:internal/modules/cjs/loader:1920
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: The module '\\?\C:\tools\scoop\persist\nodejs-lts\bin\node_modules\@microsoft\inshellisense\node_modules\@homebridge\node-pty-prebuilt-multiarch\build\Release\conpty.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 127. This version of Node.js requires
NODE_MODULE_VERSION 137. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object..node (node:internal/modules/cjs/loader:1920:18)
    at Module.load (node:internal/modules/cjs/loader:1481:32)
    at Module._load (node:internal/modules/cjs/loader:1300:12)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)
    at Module.require (node:internal/modules/cjs/loader:1504:12)
    at require (node:internal/modules/helpers:152:16)
    at new WindowsPtyAgent (C:\tools\scoop\persist\nodejs-lts\bin\node_modules\@microsoft\inshellisense\node_modules\@homebridge\node-pty-prebuilt-multiarch\lib\windowsPtyAgent.js:40:36)
    at new WindowsTerminal (C:\tools\scoop\persist\nodejs-lts\bin\node_modules\@microsoft\inshellisense\node_modules\@homebridge\node-pty-prebuilt-multiarch\lib\windowsTerminal.js:53:24)
    at Object.spawn (C:\tools\scoop\persist\nodejs-lts\bin\node_modules\@microsoft\inshellisense\node_modules\@homebridge\node-pty-prebuilt-multiarch\lib\index.js:30:12) {
  code: 'ERR_DLOPEN_FAILED'
}

I managed to get into settings fast enough to switch to Command Prompt and error went away.

I'm seeing this as well - I was seeing the issue intermittently on a couple of threads and rebooted my machine. Now it happens instantly on every thread and also on the settings menu. Occasionally I can get to the settings fast enough to bring up the setting page but then it will immediately go back to the new thread page.

Is there a way to edit the settings outside the UI?

yup. this bug is real.
What version of the Codex App are you using (From “About Codex” dialog)?
26.409.20454

What subscription do you have?
200usd
Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?
The Windows app occasionally navigates away from the active conversation and opens a brand-new thread while the current thread is still generating. This happens without any intentional mouse or keyboard input from me.

What steps can reproduce the bug?
Open the Codex app on Windows.
Open an existing thread.
Send a prompt and wait for the model to start generating.
Keep the app un/focused on that active thread.
Intermittently, the UI switches to a new blank thread on its own.