OPENAI PUB_DATE: 2026.04.11

CODEX 0.119–0.120: REALTIME V2 PROGRESS STREAMING, STRONGER MCP, AND STURDIER REMOTE/SANDBOX RUNS

OpenAI Codex shipped 0.119 and 0.120, adding Realtime V2 progress streaming and major stability fixes for remote and sandboxed workflows. The releases bring ag...

Codex 0.119–0.120: Realtime V2 progress streaming, stronger MCP, and sturdier remote/sandbox runs

OpenAI Codex shipped 0.119 and 0.120, adding Realtime V2 progress streaming and major stability fixes for remote and sandboxed workflows.

The releases bring agent quality-of-life upgrades: Realtime V2 can now stream background progress and queue follow-ups, while voice sessions default to the v2 WebRTC path for cleaner transport. Remote/app-server workflows gained egress WebSocket support, runtime remote control, sandbox-aware filesystem APIs, and an experimental exec-server. The TUI picked up nicer copy/resume/notification behavior and clearer hook visibility (0.119.0, 0.120.0).

Under the hood, Windows elevated sandbox splits, symlinked carveouts, and TLS websocket panics were fixed. Rate-limit handling in the TUI now fetches limits asynchronously and refreshes stale quotas, which lines up with questions after the April 9 limit changes Understanding the New Codex Limit System After the April 9 Update.

[ WHY_IT_MATTERS ]
01.

Realtime progress streaming and queued responses reduce perceived latency and make long-running agent work observable.

02.

Remote and sandbox fixes unstick CI/SSH workflows and reduce flaky permission errors across Windows and symlink-heavy repos.

[ WHAT_TO_TEST ]
  • terminal

    Run a remote/app-server session over egress WebSocket, try --cd forwarding, exercise the experimental exec-server, and validate sandbox carveouts with symlinks.

  • terminal

    Start a long Realtime V2 session and confirm streamed progress, queued follow-ups, and accurate TUI rate-limit updates post–April 9.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Upgrade pinned environments to ≥0.120 and re-run Windows/symlink carveout scenarios; check for any behavior shifts in tool search result ordering.

  • 02.

    Audit remote TLS websocket flows to confirm the Rustls provider fix eliminates prior panics.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Adopt MCP tools with typed outputSchema to enforce structured results in code-mode workflows.

  • 02.

    Expose Realtime V2 progress telemetry in your UI so operators can see agent work while it runs.

SUBSCRIBE_FEED
Get the digest delivered. No spam.