Codex CLI: WebSocket Proxy Support & Thread Archive Notifications

CodexView original changelog

Codex CLI 0.104.0 adds WS_PROXY and WSS_PROXY environment variable support for routing WebSocket connections through a proxy, closing a gap for users in corporate or VPN environments. The app-server now emits push notifications when threads are archived or unarchived. Command approval handling was also updated with distinct identifiers per approval step.


WebSocket Proxy Support

Codex's network layer now respects WS_PROXY and WSS_PROXY environment variables when establishing WebSocket connections. Previously, users who routed HTTP traffic through a corporate proxy found that Codex's WebSocket connections bypassed their proxy configuration entirely. This change brings Codex's WebSocket behavior into alignment with its existing HTTP proxy support.

Thread Archive/Unarchive Notifications

The app-server v2 now sends push notifications when a thread transitions between archived and unarchived states. Previously, clients had to poll periodically to detect these state changes. With event-driven notifications, clients can update their thread lists and UI state reactively.

Command Approval ID Improvements

Protocol and core components now carry distinct approval identifiers for each individual approval step within a single shell command execution. This enables scenarios where a single command triggers multiple approval gates.

Bug Fixes

Ctrl+C and Ctrl+D inputs in the resume/fork workflow now cleanly exit the working directory change prompt. A false-positive safety-check downgrade issue was resolved by prioritizing response header model data.