Stable release· Major · Confirmed
Stable 0.142.5 stops logging full WebSocket request payloads
A privacy-focused patch removes a trace log that could contain complete Responses WebSocket requests.
The behavior of the request path is unchanged, but trace output is safer: the release backports a fix that prevents full WebSocket request contents from being written to logs.
Stable release context: 1 official tag was published that UTC day (rust-v0.142.5). The full comparison contains 2 commits and 2 changed files.
Evidence
Stable 0.142.5 removes trace logging of full Responses WebSocket request payloads.Why it matters: Sensitive prompt and request contents are less likely to be exposed through verbose application traces.
Direct evidence · Confirmed
Supporting sources
- [codex] Backport websocket trace fix to release/0.142 (#30771) commit · Official
- rust-v0.142.4 to rust-v0.142.5 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: these sources establish repository and CLI release 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 | Stable · 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. |