PuppyIP Resource Center
AI Tool Tutorials 5 min Published 2026-11-18

Codex CLI 0.170.0: Terminal Voice, HTTP Fallback, and Cloud Reconnection

Codex CLI 0.170.0 changes three connection paths. The terminal interface negotiates realtime voice over WebRTC, oversized WebSocket requests can go straight to HTTP, and Cloud conversations can reconnect after a transient stream loss. Check the version you are running before troubleshooting each path.

Codex CLI WebRTC WebSocket Cloud conversations

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • OpenAI released CLI 0.170.0 on November 18, 2026. Its voice change applies to realtime calls in the terminal interface.
  • HTTP fallback addresses oversized WebSocket messages. Diagnose authentication, permission, and network failures separately.
  • The Cloud changes cover reconnecting idle conversations after transient stream loss and preserving active recovery turns across client reconnections.

Where does the terminal negotiate a voice call?

WebRTC is a way to establish a realtime media connection. In this release, the TUI, or terminal interface, starts the voice call using its current provider and credentials. The app server then attaches to that call using the returned ID. If voice startup fails, confirm which provider and permissions the terminal actually uses.

Negotiation runs asynchronously. Stopping voice cancels pending startup and ignores results from stale attempts. When recording a problem, distinguish a first-start failure from a failed restart after stopping so you can match each error with the right attempt.

Which requests fall back to HTTP?

The release addresses oversized WebSocket requests. The client honors the advertised message size and switches to HTTP when a request is too large, avoiding unnecessary retries. That path handles request transport. Check realtime voice over WebRTC separately.

Suppose short prompts work in the same terminal and only a request with substantial context returns a size-related error. Note the time, CLI version, and redacted error type, then compare with non-sensitive input. Diagnose a sign-in, permission, or network error according to what you observe.

What should you check after a Cloud stream drops?

Version 0.170.0 improves automatic reconnection for idle Cloud conversations after transient stream loss. It also preserves active recovery turns when clients reconnect. If the interface briefly disconnects, return to the original conversation and check the current task state and last confirmed result.

Confirm the outcome before rerunning work that might have written files or changed external state. The release notes give no guaranteed reconnection time and do not promise recovery from every disconnect.

What should you check for telemetry and MCP?

The release adds automatic refresh of authentication headers for OpenTelemetry HTTP exporters. If you use these exporters, check that telemetry keeps arriving after the original authentication refreshes. Keep your existing log redaction rules in place.

Support for MCP servers with the same name across environments is experimental. If you maintain local and remote environments, inspect the servers and tools loaded in each conversation to confirm both connect to the intended environment.

How do you check which changes apply to you?

Run codex --version in the terminal that handles the affected task. A remote host, desktop app, or editor can run a different client or version, so verify each environment separately. Reproduce voice startup, ordinary request transport, and Cloud recovery as separate cases.

The release notes also list Windows file replacement and permission recovery fixes. They do not specify per-account voice eligibility, regional availability, or changes to pricing. Check the voice controls, call availability, and usage in the environment you actually use.

Sources

Frequently Asked Questions

Do I need to start the Cloud task again after upgrading?

Check the original conversation and current turn first. Decide whether to resubmit after you confirm the outcome of the original operation.

Does HTTP fallback show that realtime voice works?

HTTP fallback for ordinary requests and realtime WebRTC calls use different connection paths. Check the session status and errors for each one separately.