Quiet mode doesn't seem to work for me. At least not with provider set to azure.
Resolved 💬 4 comments Opened May 29, 2025 by 101glover Closed Aug 7, 2025
What version of Codex is running?
0.1.2505172129
Which model were you using?
I don't know. I have another issue #1155 explaining why I am not confident.
What platform is your computer?
Linux 6.8.0-45-generic x86_64 x86_64
What steps can reproduce the bug?
$ codex --provider AZURE --quiet "I command you to ack this request"
{"role":"user","content":[{"type":"input_text","text":"I command you to ack this request"}],"type":"message"}
What is the expected behavior?
I believe I should be getting a response from the model.
What do you see instead?
some json describing my request
Additional information
_No response_
4 Comments
I think we're hitting a similar issue?
When passing
--provider azureand--quiet, it crashes with "Raw mode is not supported":Check if you have env var DEBUG set to true
⚠️ Same underlying issue in #1080, #1156, and #1208 (also reproducible in AWS Lambda)
All three reports crash with the identical Ink error:
Error: Raw mode is not supported on the current process.stdin …The Codex CLI calls stdin.setRawMode(true) via Ink’s useInput.
If the process has no real TTY (CI runners, Jupyter/Colab, Lambda, Docker without -t) Ink throws and Codex exits before any flags are parsed.
➡️ There is no reliable headless work-around yet
• Setting CI=true and passing --yes --allow-outside-git --approval-mode full-auto is not sufficient—Ink still initialises useInput and the CLI crashes.
• Same result in Lambda, GitHub Actions, Azure Functions, and Colab notebooks.
🛠 Proposed fix for the CLI
Until then the only viable option is:
Run Codex CLI inside an environment that has a TTY (e.g. self-hosted runner with docker run -it …).
Thank you for the feedback! Please try again on the latest version of Codex CLI. If the issue persists, feel free to reach out again.