[Windows Desktop 26.721.4979.0] Codex-spawned PowerShell crashes in ConsoleControl and shell tool returns aborted

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

26.721.4979.0 (OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0)

What subscription do you have?

ChatGPT subscription; the exact tier was not available from the local diagnostics used for this report.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

Windows PowerShell / System.Management.Automation file version: 10.0.26100.8894

What issue are you seeing?

During a Codex Desktop agent task, a shell tool invocation returned aborted, and the desktop task appeared to disconnect/reload. The invoked command did not return a lint, build, or test failure.

At the same timestamp, Windows Error Reporting recorded a real crash of the Codex-spawned powershell.exe host:

Time: 2026-07-26 20:45:46 +08:00
NameOfExe=powershell.exe
FileVersionOfSystemManagementAutomation=10.0.26100.8894
InnermostExceptionType=System.ComponentModel.Win32Exception
OutermostExceptionType=System.Management.Automation.Host.Host
DeepestFrame=Microsoft.PowerShell.ConsoleControl+<>c.<.cctor>b__106_1
ReportIdentifier=68796b42-7aa1-467d-9ef3-3f84c61a0c4c
WER bucket=73a11a25a73832c0149f0f71a664a7ef

The workspace remained intact, and shell commands worked again after continuing the task. I found no matching Codex Application Error, Application Hang, or resource-exhaustion event, and no Codex Crashpad dump. Codex Desktop log files created during the same minute were zero bytes.

This points to a transient failure in the Windows PowerShell console/host path used by the Codex shell tool. It does not appear to be a repository command failure. The timing establishes correlation; it does not prove whether the child PowerShell crash caused the desktop interruption or followed another terminal/session failure.

What steps can reproduce the bug?

This has been observed once and has not been intentionally reproduced because it interrupted an active development task.

Observed sequence:

1. Open a native Windows workspace in Codex Desktop with PowerShell as the shell host.
2. Run a sequential shell tool command containing several local package checks, approximately:

``powershell
pnpm exec prettier --write <files>; pnpm exec eslint <files>; pnpm run build; node --test <focused-test>
``

1. During the invocation, the desktop task appears to disconnect/reload and the tool result becomes aborted.
2. Windows Error Reporting records the PowerShell host crash shown above at the same time.

A long chained command may expose the problem, but that trigger has not been proven. Manual PowerShell and later Codex shell calls worked normally.

I searched existing issues using the exact ConsoleControl, System.Management.Automation.Host.Host, and b__106_1 signature and did not find a matching report. Issues #17326 and #18538 are related Windows shell-host/tool-result failures but have different exception paths and behavior.

What is the expected behavior?

A child PowerShell/console-host failure should be isolated from the Codex Desktop task. The tool should return an explicit, actionable shell-host error without aborting or disconnecting the active task, and diagnostic logs should contain usable evidence.

Additional information

The full WER report is intentionally not attached because it contains local environment details. I can provide a further redacted extract if maintainers need additional WER fields.