Codex may use shell-less V8 environment for explicit gh CLI requests

Reproduction

1. On Windows, install and authenticate GitHub CLI.
2. Confirm gh auth status succeeds in the host terminal.
3. Ask Codex Desktop to use the gh CLI.
4. Codex may attempt to execute it inside its fresh V8 orchestration sandbox.
5. That sandbox reports:

process: undefined
require: undefined
Deno: undefined
node:child_process import: failed
gh execution: failed

1. Tell Codex to use the host command-execution environment.
2. The same gh operation succeeds using the existing host authentication.

The Node-backed MCP environment was also tested and successfully resolved gh. The reproduced failure is specifically in the shell-less V8 orchestration environment.

Expected behavior

An explicit request to use gh runs in the authenticated host command environment.

Actual behavior

Codex may select its shell-less V8 orchestration environment, where gh cannot execute, requiring the user to redirect it manually.

Environment

• Codex Desktop
• Windows
• GitHub CLI 2.89.0
• Failing environment: fresh V8 orchestration isolate
• Working environment: Windows host command execution