Codex doesn't see failed state of process

Resolved 💬 5 comments Opened Nov 14, 2025 by JKamsker Closed Feb 23, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.58.0

What subscription do you have?

Pro

Which model were you using?

5.1-codex medium

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Observed multiple times: Codex invokes some shell or tool like `dotnet build` - build fails - codex be like "all good ✅ "

What steps can reproduce the bug?

Uploaded thread: 019a7eb5-4af4-7383-a9b7-6dadeb3b601b

Make it build a broken sln and it will tell you its fine

What is the expected behavior?

It seeing that the process didnt succeed.

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6644
  • #6415

Powered by Codex Action

Kruupych · 9 months ago

Same

I came to using dotnet build -p:WarningLevel=0 and now Codex sees all errors.

It seems that there is a limit on the text added to the context obtained from the command execution results.

I see two solutions for OpenAi Codex team:
1) Increase the limit.
2) If the limit is left in place, then at least make it so that 50% of the text is taken from the top (beginning of the text) and the other 50% from the end of the text, so that the model will see the result of the execution.

JKamsker · 9 months ago

@Kruupych And/or

  • always make sure the return code is present
  • Prioritize stderr
etraut-openai contributor · 6 months ago

Revisiting old (potentially stale) bug reports. Are you still seeing this with the latest version of Codex?

This would be a good issue for someone in the community to diagnose. Insights are welcome.

JKamsker · 6 months ago

No its solved i think, thanks for checking!