Exec terminal hangs on dotnet commands like build, run, and clean

What version of Codex CLI is running?

1.110.1 (61b3d0ab13be7dda2389f1d3e60a119c7f660cc3) (arm64)

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.4 high

What platform is your computer?

Darwin 25.2.0 arm64 arm

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

iTerm2 build 3.6.6

What issue are you seeing?

Codex appears to have a terminal execution issue with solution level dotnet commands.

When Codex runs commands such as:

dotnet build ExampleSolution.sln
dotnet clean ExampleSolution.sln --nologo --verbosity minimal

the command starts, but Codex may:

• show no stdout or stderr
• fail to stream normal progress output
• fail to report completion in a normal time window

The same commands complete normally in a regular terminal outside Codex.

A simple informational flags such as:

dotnet --info

did complete normally inside Codex.

This suggests the issue is not all dotnet execution. It appears more likely to affect solution level commands such as build and clean, possibly where output formatting, color, or richer terminal behavior differs from simpler commands.

Related issues:

• #14303
• #15461
• #14928

What steps can reproduce the bug?

1. Open Codex in the root of a .NET repo.
2. Ask Codex to a dotnet command like build, it will look like this maybe with some extra params and flags:

dotnet build ExampleSolution.sln

or

dotnet clean ExampleSolution.sln --nologo --verbosity minimal

1. Wait for output and completion.
2. Observe that Codex may not stream output and may not report completion within a normal time window.
3. Get the exact command fomr /ps that was ran and open a new regular terminal outside Codex, run the exact command in the same folder
4. Observe that it prints output and exits normally there.

Control case:

dotnet --info
dotnet --list-sdks
dotnet --version

These completed normally inside Codex.

What is the expected behavior?

Codex should reliably do one of these:

• stream stdout and stderr while the command runs
• or, if live streaming is not supported, still detect completion and return the final result when the command exits

Additional information

This looks like a Codex terminal bridge issue rather than a dotnet issue because:

• the same solution commands work outside Codex
• simple dotnet flags such as dotnet --info work inside Codex
• Actual dotnet commands such as build, run, and clean did not

Possible direction for investigation:

• output handling differences between simple dotnet commands and solution level commands
• color or rich terminal formatting from dotnet commands may be impacting codex bridge