Codex CLI 0.170.0 fixes WebSocket fallback, MCP OAuth races and sandbox permission bugs
Codex CLI 0.170.0 includes bug fixes for WebSocket fallback, MCP OAuth credential races, Cloud reconnection, Windows sandbox handling and permission settings.
Codex CLI 0.170.0 lists a set of bug fixes covering WebSocket fallback, MCP OAuth credential races, Cloud reconnection, Windows sandbox handling and sandbox permissions. The release was published on GitHub on 18 November. The new features in the same release are a WebRTC negotiation path for realtime voice calls in the TUI, refreshable authentication headers for OpenTelemetry HTTP exporters, and experimental support for identically named MCP servers across environments.
According to the pull request linked from the release, a WebSocket close with code 1009 that arrives before any text indicates that the request exceeds the peer's message size limit. Retrying over another WebSocket does not address that limit, so the earlier code would use up its WebSocket retries before switching to HTTP. The change classifies those early size rejections as requiring HTTP fallback, including during prewarming. It leaves ordinary retry behavior alone for size closes that come after a text frame and for other close codes. A companion pull request, #60841, addresses requests that exceed the server's advertised WebSocket message size limit. The client reads the x-codex-websocket-max-message-bytes header from the handshake response and checks the serialized request's byte length before sending. An oversized request therefore goes straight to the existing HTTP fallback without first being uploaded. Missing or invalid limits are ignored. The test described in that pull request advertises a one-byte limit and checks for zero WebSocket generation requests and one HTTP request.
The MCP OAuth fixes are described more briefly. The release lists races during cancellation, login and logout, and it links two pull requests. One, #60849, is titled as protecting MCP OAuth persistence from stale credential writes. The other, #60981, makes reactive MCP OAuth refreshes cancellation-safe. The release notes do not say what a user would have seen when these races hit, so the release describes the class of bug without showing its symptoms.
The Cloud and Windows items are similarly terse. Idle Cloud conversations now reconnect after transient stream loss, according to pull request #60969. Active recovery turns are preserved when clients reconnect, according to #61014. On Windows, the release lists fixes to file replacement, to file permissions during repeated sandbox setup, and to runtime registration after service privilege errors. The commit titles behind these say Windows atomic writes were fixed and that permissions are preserved during repeated sandbox setup. The release notes themselves give no detail on how those failures appeared.
The sandbox permission fixes deal with an issue in which permission updates and child threads were losing existing sandbox restrictions. The changelog ties this to several related commits. One normalizes permission updates when session settings are admitted. Another preserves legacy sandbox templates in TUI permission conversions. A third removes the legacy sandbox policy setter from Config. A companion documentation change, #61133, updates the sandbox documentation to explain permission profiles and filesystem rules. The release does not explain how those profiles differ from the older policy form.
Smaller fixes round out the list. Duplicate file search results from overlapping roots were removed, and thread search snippets now work for queries containing whitespace. The release also includes changes that appear only in the changelog, such as a fix for code-mode session admission retries on proxy HTTP 503 responses. The changelog lists the contributors by GitHub handle.
What changed
Codex CLI 0.170.0 fixes WebSocket fallback, MCP OAuth credential races, Cloud reconnection, Windows sandbox handling and sandbox permission loss.
Type: Other · Applies to: Codex CLI 0.170.0, Windows, MCP OAuth
Why it matters
Teams running Codex CLI with MCP servers, Windows machines or sandboxed sessions get fixes in areas where permission or credential errors could affect their work.
What you can do
Teams running Codex CLI on Windows or with MCP OAuth should update to 0.170.0 and recheck their sandbox and sign-in behaviour.
Original source
- github.comRelease 0.170.0 · openai/codex · GitHub
- github.comFall back to HTTP immediately for oversized WebSocket requests by copyberry[bot] · Pull Request #60840 · openai/codex · GitHub
- github.comHonor advertised WebSocket message size limits by copyberry[bot] · Pull Request #60841 · openai/codex · GitHub
Where we saw it
Codex CLI releases
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works