123 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-07
stories 84

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

CODEX FIXES PROXY ATTRIBUTION BUG, NODE SDK PATCHES STREAM CORRUPTION

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

Concurrent network requests in Codex conversations were getting routed to the wrong executors, and the Node SDK was silently corrupting streamed assistant arrays.

The Codex team shipped a critical fix [1] that attributes network requests to the exact executor on Linux, solving a proxy routing problem where concurrent curl calls within the same conversation couldn't be distinguished by the Guardian proxy. This surfaces a broader theme across both desks: data integrity under concurrent conditions. The Node SDK hit the same wall [6] when streaming assistant array deltas, where out-of-order indices were being appended instead of assigned, landing entries at wrong positions and corrupting state. Both fixes are small but ship against the kind of bugs that only surface under load, so they matter. On the Codex side, the team also moved Apps guidance into persistent world state [2], ensuring the model gets proper tool instructions even when the MCP recovers mid-turn, and shipped canonical command execution items [3] to standardize the event model across app-server v2. The Node SDK backfilled two more safety patches: Next.js got upgraded to 15.5.16 to close a flagged CVE in examples [5], and the streaming layer now treats keepalive events as no-ops instead of crashing the accumulator [7]. Autocomplete insertion in Codex also got stricter token range handling [4] to prevent cursor position ambiguity from replacing the wrong token.

Action items

References

  1. [1] fix: attribut network requests to the exact exec on linux (#29697) openai/codex ↗
  2. [2] Make Apps guidance react to MCP availability (#30226) openai/codex ↗
  3. [3] feat(core): emit canonical command execution items ↗ openai/codex
  4. [4] Use popup token ranges for autocomplete insertion ↗ openai/codex
  5. [5] fix: upgrade next to 15.5.16 in examples ↗ openai/openai-node
  6. [6] fix(assistants): place array delta entries by index instead of appending ↗ openai/openai-node
  7. [7] Handle keepalive events in Responses streams ↗ openai/openai-node

Quick answers

What shipped in OpenAI on July 7, 2026?
Concurrent network requests in Codex conversations were getting routed to the wrong executors, and the Node SDK was silently corrupting streamed assistant arrays. In total, 41 commits, 41 pull requests, and 2 releases landed.
Who contributed to OpenAI on July 7, 2026?
5 developers shipped this update, including owenlin0, charliemarsh-oai, sonukapoor, spokodev, and koriyoshi2041.
What were the notable OpenAI updates?
fix: attribut network requests to the exact exec on linux (#29697), Make Apps guidance react to MCP availability (#30226), and feat(core): emit canonical command execution items.