Codex can no longer be invoked be script

Resolved 💬 2 comments Opened Oct 22, 2025 by alex-taffe Closed Oct 22, 2025
💡 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.47.0

What subscription do you have?

ChatGPT Business

Which model were you using?

gpt-5-codex

What platform is your computer?

Darwin 25.0.0 arm64 arm

What issue are you seeing?

I have a Python script that is invoking codex. Codex then spits out json, which is parsed by the python script. Codex 0.42.0 works correctly. 0.43.0-0.47.0 are spitting out the error:

proto error (Error: stdout is not a terminal)

That is correct, it is not a terminal, which is what I want.

What steps can reproduce the bug?

On codex >= 0.43.0, invoke the following script with:

python3 ai_issue_helper.py "How are you today"

ai_issue_helper.py

This was tested on macOS, but in production we use linux. You will get

[auth] Codex status ok: already authenticated
Error: stdout is not a terminal

What is the expected behavior?

The script should output what codex has to say, not something about a stdout not being a terminal

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 10 months ago

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

  • #3497
  • #3496
  • #3843
  • #3492
  • #5338

Powered by Codex Action

alex-taffe · 10 months ago

Turns out codex exec exists, closing