150 wires and counting

$ follow OpenAI

Keep up with OpenAI in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-07-01
stories 6

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

CODEX PATCHES WEBSOCKET LOGGING LEAK

By RepoJournal · Filed · About OpenAI · Composed from the cited sources · methodology

Full request payloads were bleeding into trace logs across WebSocket connections, and Codex 0.142.5 just plugged it.

Codex shipped an emergency patch [1] that prevents complete Response objects from being written to trace logs during WebSocket operations. This follows an earlier fix [2] that caught one trace statement, but a second unfiltered log point was still leaking full payloads into observability pipelines. The fix is already backported to the 0.142 release line [1], so if you're running production Codex instances on that channel, the patch is ready now. In parallel, the team updated safety notice wording in the TUI biosafety block [3] to remove outdated copy about Trusted Access applications. Alpha builds continue rolling forward with 0.143.0-alpha.32 [4] available for testing.

Quick answers

What shipped in OpenAI on July 1, 2026?
Full request payloads were bleeding into trace logs across WebSocket connections, and Codex 0.142.5 just plugged it. In total, 2 commits, 2 pull requests, and 2 releases landed.
What were the notable OpenAI updates?
0.142.5, fix(core) Remove full text websocket trace (#30757), and [codex] Update safety notice wording (#30645).