What issue are you seeing?
WinGet release PRs for Codex repeatedly fail automated executable validation and require manual moderator approval. This delays updates for users who installed Codex through WinGet.
Current example:
microsoft/winget-pkgs#409235
The validator launches every executable contained in the Windows archive without arguments. The observed failures are:
codex.exe: Error: stdout is not a terminalcodex-command-runner.exe: Error: runner: no pipe-in providedcodex-windows-sandbox-setup.exe: Error: helper_request_args_failed: expected payload argument
The PR consequently receives the Validation-Executable-Error label and has to wait for manual approval even though the installer, hashes, and manifest validation pass.
This has happened repeatedly across recent Codex releases, so WinGet users cannot receive updates promptly.
Expected behavior
Codex WinGet release PRs should be able to pass automated validation without manual approval.
Possible solutions might include:
- Configure validation to probe the main executable using
codex --version.
- Add a safe
--version probe to bundled helper executables if WinGet must execute them.
- Mark or exclude protocol-only helper executables from launch validation.
- Coordinate a package-specific validation rule with the WinGet maintainers.
The helpers should not need to return success when launched without their required protocol arguments; using an explicit version probe or excluding them would be preferable.
Additional information
A previous issue was closed after the affected manifests were manually merged, but the reporter explicitly noted that the validation pipeline was still failing:
#33056
What issue are you seeing?
WinGet release PRs for Codex repeatedly fail automated executable validation and require manual moderator approval. This delays updates for users who installed Codex through WinGet.
Current example:
microsoft/winget-pkgs#409235
The validator launches every executable contained in the Windows archive without arguments. The observed failures are:
codex.exe:Error: stdout is not a terminalcodex-command-runner.exe:Error: runner: no pipe-in providedcodex-windows-sandbox-setup.exe:Error: helper_request_args_failed: expected payload argumentThe PR consequently receives the
Validation-Executable-Errorlabel and has to wait for manual approval even though the installer, hashes, and manifest validation pass.This has happened repeatedly across recent Codex releases, so WinGet users cannot receive updates promptly.
Expected behavior
Codex WinGet release PRs should be able to pass automated validation without manual approval.
Possible solutions might include:
codex --version.--versionprobe to bundled helper executables if WinGet must execute them.The helpers should not need to return success when launched without their required protocol arguments; using an explicit version probe or excluding them would be preferable.
Additional information
A previous issue was closed after the affected manifests were manually merged, but the reporter explicitly noted that the validation pipeline was still failing:
#33056