Signals

2026-10-13 / Codex

Interactive Codex shares a server that can move beyond its CLI pin

Edited by Michael Ruescher

From 0.157.0 (2026-09-25), eligible interactive launches use a shared background app server. At stable 0.162.1, a newly seeded eligible npm or Homebrew server package can follow latest independently of the CLI, retaining the environment from server startup. Explicit standalone-release pins behave differently; codex exec does not use this daemon path. The stable CLI uses a service whose lifecycle contract remains experimental.

What this changes for operators

  • Interactive fleets and evaluation owners: run 0.162.1 and record both codex --version and codex app-server daemon version. Use --no-daemon for a fixed per-launch baseline, or set {“updater”:{“autoUpdateEnabled”:false}} in CODEX_HOME/app-server-daemon/settings.json and restart the daemon.
  • Restart after changing inherited credentials or PATH. Restart keeps the selected server package; it does not undo an earlier update. Shared service operation replaces repeated startup with environment and update administration. Disabling updates returns patch scheduling to the owner.
  • Keep the updater off where managed network policy must hold on 0.162.1. A stable containing d570b3632b100e36f931797cdbdb8906d0fcafa8, now preview-only, plus blocked-network and failed-config probes would settle enforcement; a recorded pinned-install update trace would settle actual update behavior.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-13-codex-interactive-server-has-its-own-version

Research evidence and publication history are open in the repository.