[Windows Desktop] Every completed response causes a system-wide stall and Event 1000 from bundled serialport.node

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

26.707.72221

What subscription do you have?

Pro

What platform is your computer?

Windows 11 Pro (latest updates)

What issue are you seeing?

Codex version

OpenAI Codex Desktop 26.707.9981.0, Windows x64

Problem

Every time an assistant response completes, the Windows desktop briefly becomes
unresponsive. The mouse cursor and other applications stall for approximately
half a second to one second.

The problem occurs with plain text responses.

Codex CLI does not reproduce the problem.

Windows event

A new Application Error, Event ID 1000, is recorded after responses:

• Application: ChatGPT.exe
• Exception code: 0xc06d007f
• Faulting module: unknown
• Windows error represented by the delay-load exception: 127 / procedure not found

Minidump findings

A WER minidump indicates that the exception occurs while loading this bundled
native module:

@worklouder/device-kit-oai
-> @worklouder/wl-device-kit
-> @serialport/bindings-cpp
-> serialport.node

The failing delayed import is:

node.exe!napi_module_register

The bundled serialport.node requests Node/N-API symbols from node.exe, but those
symbols cannot be resolved in the Codex Desktop Electron host. The Codex Micro
service loads this Work Louder device integration and calls its status/lighting
path when task state changes, which appears to explain why the exception occurs
after responses.

Additional observations

• The same exception is recorded repeatedly from the same ChatGPT.exe process.
• Disabling per-exception WER dump creation substantially reduces the freeze,

but the Event 1000 exception and smaller stall remain.

• Before disabling dumps, Windows created an approximately 11 MB dump after

each occurrence.

• No equivalent exception or stall occurs in Codex CLI.
• Reinstalling or restarting Codex does not resolve it.
• This may be related to #16374, but that report does not identify this specific

native-module failure.

What steps can reproduce the bug?

Reproduction steps

1. Open Codex Desktop on Windows.
2. Open any task.
3. Send a message and wait for the assistant response to complete.
4. Observe a brief system-wide stall.
5. Repeat with additional messages.
6. Check Windows Event Viewer under Windows Logs > Application.

What is the expected behavior?

Expected behavior

Codex Desktop should not load the optional Codex Micro hardware integration on
systems that do not use the device. A failure to load that integration should
also be caught and disabled instead of raising a native delay-load exception
after every response.

Additional information

_No response_