Codex App: intermittent delay before bundled pwsh.exe process creation

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

Not available from the desktop executable metadata in this session

What subscription do you have?

Not available to the reporter in this session

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Controlled diagnostic summary

An intermittent Codex App execution-host delay was observed before the bundled pwsh.exe process was created for a harmless, no-filesystem PowerShell workload. The diagnostic program has stopped locally; this report requests read-only platform correlation only.

Frozen evidence reference

• Package: MCAID-AL-LE01 Platform Telemetry Escalation Evidence Package v1.0
• Package ID: CSA-MCAID-AL-TECH-ESC-2026-294
• SHA-256: B800CE8679E2DA044E81376246F2CAB3F2F183ACF86AA4A77C3AD60DB08612D1

Material observed event (Unix epoch milliseconds)

The expected marker and usable result returned. No residual PowerShell child process was observed after completion.

Observed process relationship: pwsh.exe PID 12292; immediate parent codex.exe PID 18332.

Observed fact: 104.276 seconds elapsed from external invocation to pwsh.exe process creation in this no-filesystem event.

Inference, not a fault assertion: the responsible owner is somewhere in the upstream request, queue, dispatch, or process-launch lifecycle. Immediate parentage does not establish that codex.exe caused the delay.

Local paths and user-identifying data have been redacted because this is a public issue.

What steps can reproduce the bug?

1. In the Codex desktop app, invoke a harmless no-filesystem PowerShell command that records an external start time and emits an inner timestamp at its first instruction.
2. Capture the parent-visible completion time.
3. For the material event above, process metadata showed that the bundled pwsh.exe process was not created until 104.276 seconds after external invocation, although the command then completed normally.
4. The behavior is intermittent. Please do not treat this report as a request for repeated local reproduction or any local remediation.

What is the expected behavior?

Process creation should be dispatched promptly. If an intermittent host-managed delay occurs, the platform should be able to correlate it with request acceptance, queueing, scheduling, dispatch, launch request, and process creation so an approved remediation or workaround can be identified.

Additional information

Read-only platform correlation requested

Please provide, if available:

• request or correlation identifier;
• request acceptance timing;
• queue entry and exit timing;
• scheduler and dispatch timing;
• process-launch-request and process-creation correlation;
• relevant retry, backoff, throttle, or resource-wait evidence;
• relevant host warnings or errors;
• correlated known-platform incident information; and
• an approved remediation/workaround and rollback information, if one exists.

Boundaries

This is a diagnostic escalation only. No remediation, configuration change, security-policy change, additional local diagnostics, Alabama curriculum work, Site Builder action, deployment, or publication is authorized by this report. The frozen evidence package and its controlled findings are available through the authorized support channel if further review is needed.

No repository files, tests, or code entry points are named. Start by reviewing the frozen evidence package and the Windows process-timing sequence, then check whether request, queue, dispatch, launch, and process-creation correlation is available. Done would require a correlated cause or approved workaround, but the issue provides no repository-level acceptance test.