What Codex Non-Interactive Install Is Really For

A build machine does not know how to press “yes.” That sounds obvious until a deployment stops at 2:13 a.m. because an installer politely asked whether it should deal with an older npm-managed Codex on PATH. Nothing is broken. Nothing is compiling. The machine is just waiting, forever, for a person who is asleep.

That is the boring, very real problem behind one line in the Codex CLI 0.135.0 release notes: install.sh and install.ps1 now support non-interactive installation when CODEX_NON_INTERACTIVE=1 is set.

It is not a new model. It is not a magic unattended login. It is an installer behavior change. And for teams trying to run coding agents inside CI, containers, remote workers, or auto-update flows, that small change matters.

The plain version

Interactive install means the script may stop and ask a question. Non-interactive install means the script must not stop for a question. It should either finish successfully or fail with a clear exit code.

On macOS and Linux, the shape is:

CODEX_NON_INTERACTIVE=1 curl -fsSL https://chatgpt.com/codex/install.sh | sh

On Windows PowerShell, it is the same idea:

$env:CODEX_NON_INTERACTIVE = "1"
irm https://chatgpt.com/codex/install.ps1 | iex

The installer treats 1, true, and yes as enabled values. Once enabled, yes/no prompts do not ask the terminal for input. The script takes the safe default path instead of hanging.

What changed in Codex 0.135.0

The relevant work landed in OpenAI’s public Codex repository in PR #21567. The PR text explains the issue plainly: standalone installers could pause after installation to ask about older managed installs or launching Codex. That made unattended bootstrap and update flows unreliable.

The same change also added CODEX_RELEASE, so automation can choose a version through the environment:

CODEX_RELEASE=0.135.0 CODEX_NON_INTERACTIVE=1 curl -fsSL https://chatgpt.com/codex/install.sh | sh

That version pinning is not decoration. If you are building a Docker image, preparing a CI runner, or keeping a fleet of developer machines consistent, “latest” is convenient but not always acceptable. A pinned version gives you rollback and repeatability.

Another PR, #24637, wired this into Codex’s standalone update path. The point was simple: if the CLI itself tells you an update is available and runs the installer, that update should not fall into an installer prompt halfway through.

What it does not do

This part is worth spelling out because “non-interactive” often gets misunderstood.

• It does not sign you into ChatGPT.
• It does not provide an API key.
• It does not approve code changes.
• It does not bypass project permissions.
• It does not mean “say yes to every dangerous prompt.”

In fact, the PR notes are careful about destructive cases. Older Windows standalone layouts that require a migration still need an interactive confirmation; the non-interactive path does not silently replace them. That is the right design. In automation, a clean failure is much better than a quiet destructive action.

Where this shows up in real work

The most common home for non-interactive install is CI/CD. A GitHub Actions runner or Jenkins worker may need Codex installed before running a review job, a code-mod task, or a test-repair agent. If the installer asks a question, the job is effectively dead.

Docker images are another obvious place. You want a Dockerfile to build the same way every time. A prompt inside docker build is not a user experience issue; it is a broken build.

There is also fleet setup. A company might provision dozens of MacBooks, Linux workstations, or remote build boxes with the same toolchain. MDM, Ansible, shell bootstrap scripts, and cloud-init all prefer commands that return an exit code, not commands that ask the room a question.

Then there are agent workers. This is where the Codex update becomes more interesting. A coding agent runner may be created on demand, handed a repository, asked to fix something, and destroyed after the job. That machine does not need a friendly installer. It needs a predictable bootstrap path.

Why this tiny feature fits the bigger Codex direction

The WeChat article that triggered this discussion focuses on Codex CLI 0.135.0 as a bigger release: richer codex doctor diagnostics, stronger Vim behavior, named permission profiles, Python SDK sandbox presets, dedicated SQLite-backed memory state, WebSearch as an extension, and early Goal Extension work.

Non-interactive install sits quietly next to those items. It is less exciting than goal-driven agents. But it belongs to the same direction. Codex is no longer just “a terminal app a developer opens by hand.” It is becoming infrastructure for running coding agents in controlled environments.

Infrastructure has different standards. It must install cleanly. It must update without getting stuck. It must be diagnosable. It must respect version pins. It must fail loudly when it cannot proceed safely.

That is why CODEX_NON_INTERACTIVE=1 is more than a convenience flag. It is one of those small switches that tells you a tool is being prepared for unattended work.

When you should use it

Use it when no human will be watching the terminal: CI jobs, Docker builds, remote worker bootstrap scripts, auto-update flows, cloud dev boxes, lab machines, and repeatable internal setup scripts.

Do not rush to use it for your first personal install. If you are setting up Codex on your own laptop and want to understand what it changes, the interactive path is still friendlier. Read the prompts. Check PATH. Make sure you know whether npm, Homebrew, or the standalone binary is the one being used.

The rule is simple: humans get prompts; machines get exit codes.

That is the whole point of this update. A coding agent cannot be useful overnight if its installer is waiting for someone to press a key.

Sources

• OpenAI Codex CLI 0.135.0 release notes, May 28, 2026
• openai/codex PR #21567: add noninteractive install script mode
• openai/codex PR #24637: run standalone updates noninteractively
• Codex install scripts: install.sh and install.ps1
• AI潮局 WeChat article: “Codex CLI 0.135：OpenAI在终端战场的又一次进攻”