Alpha· Major · Confirmed
Remote code mode arrives over WebSockets
App server can connect to remote code-mode hosts, side conversations stay open, and tool and plugin execution gain stronger controls and provenance.
The headline change lets app server connect to a separately hosted code-mode process over WebSockets. The transport keeps the existing framed protocol, shares one bounded connection across threads, follows configured proxy and TLS policy, and rejects browser-origin handshakes.
The same prerelease progression keeps TUI side conversations open while users switch to their parent thread, adds configuration switches for update-plan and multi-agent waiting tools, and preserves trusted plugin-script attribution through command execution and approval records.
Custom Responses providers can now opt into standalone web search. That change appears in the main alpha.5-to-alpha.6 line and in a separate alpha.3.1 branch tag published after the previous catalog run.
Release context: the main rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison contains 55 commits and at least 300 changed files. The separate rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.3.1 comparison contains 2 commits and 21 changed files.
Evidence
App server can connect to remote code-mode hosts over WebSockets.Why it matters: Code-mode execution can run behind a separately hosted process while app-server threads share one bounded, proxy-aware connection.
Direct evidence · Confirmed
Supporting sources
- Support remote code-mode hosts in app-server (#35098) commit · Official
- Add WebSocket transport to the code-mode host (#35078) commit · Official
- rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
TUI side conversations stay open when users switch to the parent thread.Why it matters: Users can move between a side conversation and its parent without closing either one, using a configurable shortcut.
Direct evidence · Confirmed
Supporting sources
- Keep side conversations open when switching threads (#35011) commit · Official
- rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Codex can hide update-plan and multi-agent wait tools through configuration.Why it matters: Managed or specialized environments can remove tools they do not want agents to see or call instead of relying only on prompt guidance.
Direct evidence · Confirmed
Supporting sources
- Allow disabling the update_plan tool (#35054) commit · Official
- Allow disabling the multi-agent wait tool (#34887) commit · Official
- rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Trusted plugin scripts carry attribution through execution and approval records.Why it matters: Command history, app-server events, approvals, and guardian assessments can identify the verified plugin and script behind a command while unsafe paths fail closed.
Direct evidence · Confirmed
Supporting sources
- Add trusted plugin script attribution (#35016) commit · Official
- Attribute command executions to trusted plugin scripts (#35020) commit · Official
- Preserve plugin attribution across command approvals (#35029) commit · Official
- rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Custom Responses providers can opt into standalone web search.Why it matters: Compatible custom providers can expose the standalone web-search tool and receive search requests through their own endpoint and authentication.
Direct evidence · Confirmed
Supporting sources
- Allow custom providers to opt into standalone web search (#34846) commit · Official
- rust-v0.146.0-alpha.4 to rust-v0.146.0-alpha.6 comparison tag-compare · Official
- rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.3.1 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: these sources establish repository and CLI prerelease activity. They do not, by themselves, prove that the same changes were live in Codex Desktop.
Availability by surface
| Surface | Status | Claim-level evidence |
|---|---|---|
| CLI | Prerelease · Documented · General |
|
| Desktop | Unknown · Unknown · Unknown |
|
| IDE | Unknown | No central-claim assertion recorded. |
| Cloud | Unknown | No central-claim assertion recorded. |
| Mobile | Unknown | No central-claim assertion recorded. |