Windows shell commands hang with no output in Codex desktop task

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

26.814.41957

What subscription do you have?

Pro

What platform is your computer?

Windows 11

What issue are you seeing?

I treated the screenshot as ticket evidence only. The reported issue is: Success Center Attendance does not show elapsed ACE study time when a student checks out after working hours, and the attendance system does not reset after 12:00am when a student forgets to clock out.
I tried to inspect the repo, but the command runner is currently hanging even on trivial commands like echo ok, dir, and targeted rg searches. I cancelled all running sessions cleanly, so nothing is left active.

What steps can reproduce the bug?

I tied to start new chats in a project and all the new chats can't do anything, I ran a read only thing in a an existing chat i was in eariler today and it can still run read only commands and edit files normally.

It seems to be with new chats

1. Open a Codex task with workspace set to:

C:\Users\kc80384\source\repos\BlazorApps

1. Ask Codex to scan the repo for a term, for example:

"can you scan this repo for SucessCenter?"

1. Codex runs basic shell commands such as:

rg -n "SucessCenter|SuccessCenter" .
cmd /c dir /b /ad
cmd /c echo ok

1. Observe that the commands never return usable output. Even simple commands like

"cmd /c echo ok" hang until manually interrupted.

What is the expected behavior?

Codex should return output from basic shell commands, especially simple commands like "cmd /c echo ok" or "dir /b".

Additional information

_No response_