Codex can't run echo $env:PATH

Open 💬 4 comments Opened Mar 9, 2026 by davidgilbertson

What version of Codex CLI is running?

codex-cli 0.111.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.4

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I just asked a basic question about my environment and all commands it tried seemed to fail, even down to the simplest echo $env:PATH.

What steps can reproduce the bug?

Uploaded thread: 019ccff6-be83-7ab1-a4a2-226f010ae5bb

What is the expected behavior?

Not only should these not fail, but they shouldn't hang if they don't work.

A human knows that if they run echo $env:PATH it will almost certainly be done in a second, and if it isn't, a human is smart enough to know that something fishy is going on and thus abort the attempt. AI should be able to as well. If the harness said to the LLM "hey you ran echo $env:PATH 10 seconds ago and it hasn't returned yet, you wanna wait or kill it?" I'm pretty sure you'd get a smart answer out of the LLM.
With any attempt at running a command, the LLM could provide a 'check-in' time. Not quite a timeout, but an opportunity to decide whether to wait another n seconds or kill it and try something else (perhaps with partial results if the command results in some stream of output).

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗