Codex CLI 0.170.0 Fixes MCP and Sandbox

By Rogier Muller11.18.26
Codex CLI 0.170.0 Fixes MCP and Sandbox

0.170.0 puts MCP credential races, sandbox permission preservation, and Cloud reconnection ahead of the flashier TUI voice work in OpenAI's Codex changelog. The Codex CLI GitHub release trail is useful if you want the linked pull requests, but the release note itself is clear enough: this update is mostly about keeping existing workflows connected while preserving auth and sandbox state.

Question Answer
Who must act No mandatory action is stated; Codex CLI users can install 0.170.0 with npm install -g @openai/codex@0.170.0.
What changes for them MCP OAuth races, Cloud reconnection, Windows sandbox setup, and oversized WebSocket handling are fixed.
Who can skip Users unaffected by MCP OAuth, Cloud conversation reconnects, Windows sandbox setup, or TUI voice can wait.

Read the release as reliability work

The headline feature is WebRTC negotiation for realtime voice calls in the TUI. That is visible product work, but the stronger engineering signal sits in the fixes around MCP OAuth, sandbox restrictions, and reconnection behavior.

The release also adds automatically refreshed authentication headers for OpenTelemetry HTTP exporters. That matters when traces leave the local process over HTTP and the exporter needs fresh auth without manual header handling.

The note does not promise a new workflow model. It says several existing paths should fail less often.

Rolling this out in your team?

We train engineering teams on their own codebase in two days. Codex setup, shared rules and review included.

Keep MCP environments distinct

Codex CLI 0.170.0 adds experimental support for using identically named MCP servers across environments. That is narrow, but useful when a repo has a local server and a production-facing server with the same logical name.

The word experimental matters. Same-named servers can now be separated by environment, but the release note does not say this is a stable config contract for every setup.

A safe habit is to make the environment boundary obvious in review. This is the Review step in our methodology: check that the agent used the intended external system before accepting the result.

Check the paths that used to break

Several fixes are about preserving boundaries under stress. The one to read twice is the fix for permission updates and child threads losing existing sandbox restrictions, because sandbox restrictions are part of the safety boundary.

Area Before 0.170.0, according to the release note In 0.170.0
Oversized WebSocket requests Requests could retry unnecessarily. They fall back to HTTP immediately and honor advertised message size limits.
MCP OAuth Credential writes could race during cancellation, login, and logout. OAuth persistence and reactive refreshes are made cancellation-safe.
Cloud conversations Transient stream loss could interrupt active recovery. Idle conversations reconnect and active recovery turns are preserved.
Windows sandbox setup File replacement, permissions, and runtime registration could fail. Atomic writes, permission preservation, and registration recovery are fixed.

This is the part of the release to connect to existing CLI workflows. If a workflow relies on MCP access or sandboxed edits, test that boundary before the nicest demo path.

Try 0.170.0 in one repo

Use the Codex CLI GitHub links for individual pull requests only after a local smoke test gives you a reason to dig. The changelog is the better first pass, and the install command is the concrete artifact from the release.

npm install -g @openai/codex@0.170.0
  1. Install 0.170.0 in one repo where Codex already runs, then record the version change in the same place you track tool updates.
  2. Re-run one MCP path that exercises cancellation or login, especially if the repo uses OAuth-backed MCP servers.
  3. Re-run one sandboxed edit or search flow and check that existing permission restrictions still hold after the session changes.

If you followed the previous release for workspace tabs, Codex CLI 0.169.0 Adds Workspace Tabs is the nearby context. 0.169.0 improved how work is organized in the TUI; 0.170.0 is more about keeping the underlying execution path stable.

Further reading

Next step

Install 0.170.0 in one existing repo and test the MCP or sandbox path that would be most expensive to debug after it breaks.

Train your team on Codex

Two days on your team's own repository, onsite or remote, with a written proposal before you commit.

Book a call

Prefer to measure first? Take the free team check.