Windows runner pipe-in timeout leaves process status unknown and returns no exec session ID

Summary

A read-only command in Codex's managed Windows execution environment failed after a 15-second runner pipe-in connection timeout. No PID or exec session ID was returned, leaving no addressable session to inspect or cancel with the available tools.

Feedback was submitted successfully.
Feedback ID: 01a07059-5e7d-7983-a001-8c21c5b05245

Environment

• Windows, managed Codex execution using exec_command/use_default.
• Exact app and bundled Codex versions: not collected.
• Operation: PowerShell Select-String reading a local Python source file.
• No lab program or trading operation was requested by this command.

Observed failure

Command recorded: 2026-09-06T18:35:27.267Z
Error recorded: 2026-09-06T18:35:42.678Z
Reported duration: 15.4 seconds.

Original error:

exec_command failed: CreateProcess { message: "Rejected(\"Failed to create unified exec process: timed out after 15000ms connecting runner pipe-in\")" }

No PID, numeric exec session_id, or running functions cell_id was returned.

The wrapper failed, but the available transcript does not establish whether an underlying Windows process was created or subsequently closed. This is an unknown state, not a claim that a process is still running.

Correlation details

Parent task/session:
01a07059-5e7d-7983-a001-8c21c5b05245

Agent task:
01a077ae-e144-70f1-b8f3-7c5c6eb0b20b

Tool wrapper call ID:
call_ekmEIv6MTI4gOU1s80w0lklJ

Result item:
ctco_01a07801-3ed6-7ab1-8a2b-79fd00a74c8d

The call ID identifies the functions.exec wrapper, not an exec session ID.

Expected behavior

On a runner connection timeout, Codex should either confirm that no child process was created, confirm cleanup, or provide an addressable request/session and a supported status/cancellation mechanism.

Requested help

Please correlate the failed call with its internal runner invocation and clarify:

1. Whether a child process was created.
2. Its terminal state and any available cleanup evidence.
3. The supported recovery procedure for managed use_default execution.

A separate read-only invocation failed with CreateProcessAsUserW / WinError5. Its relationship to this timeout is unknown.

The original command has not been retried for this status investigation. Please recommend recovery through supported platform mechanisms, without administrator rights, Desktop switching, or reduced isolation.

No repository file or test is named. Start with the managed Windows exec_command/use_default path and correlate the listed wrapper call, result item, and runner invocation; done means determining whether a child process was created, its terminal or cleanup state, and the supported recovery and status/cancellation mechanism.