New gpt-5-codex model thinks that tsc and eslint commands are stalled

What version of Codex is running?

codex-cli 0.36.0

Which model were you using?

gpt-5-codex

What platform is your computer?

Darwin 24.6.0 arm64 arm

What steps can reproduce the bug?

I have an npm script that looks like this:
"lint": "tsc -p tsconfig.json --noEmit && eslint --config eslint.config.mjs \"shared/**/*.ts\" \"src/**/*.ts\" \"tests/**/*.ts\"",

I asked the new gpt-5-codex model to run the script, and it thinks that the script is stalling.

This is a consistent issue, it happens every time.

When I use the regular gpt-5-high model, it works fine.

Thinking output from the gpt-5-codex model:

thinking
Running linter command    
                                       
thinking
Monitoring command execution status
                                       
thinking
Waiting for process completion
                                       
thinking
Waiting for linter or build to complete
                                     
thinking
Waiting for process output           
                                          
thinking
Evaluating process status                 
                                          
thinking
Retrying command execution                
                                              
thinking
Considering possible watchers                 
                                              
thinking
Assessing potential stuck compilation
                                              
thinking
Checking for large output or degrade issue
                                              
thinking
Investigating TypeScript compilation delay
                                   

What is the expected behavior?

The gpt-5-codex model should be able to successfully run tsc and eslint commands.

What do you see instead?

The gpt-5-codex model thinks that the tsc and eslint commands are stalled.

Additional information

_No response_