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-10-08
stories 125

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Codex builds arrive via Bazel, Guardian retries stop inheriting stale reviews

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

Codex is standing up a full Bazel release path beside Cargo, while a Guardian fix stops invalidated reviews from being replayed into retries and openai-node repairs how inferred upload filenames are decoded.

Roll back stale Guardian reviews before reusing reviewer history openai/codex

by copyberry

Authorization is now validated while the reviewer is reserved, before its history checkpoint is published, so a decision invalidated by a mid-flight authorization update no longer leaks into the retry. Stale attempts roll back to the last committed review, which preserves earlier valid context across repeated invalidations.

Add Bazel release staging archives openai/codex

by copyberry

New runtime_package targets cover combined, primary, app-server, and Windows helper bundles plus per-binary release archives, with release settings applied automatically. Unstripped binaries are retained alongside macOS dSYM or Windows PDB symbols, and dSYM bundles are validated to contain nonempty DWARF data; a debug mode speeds up package smoke builds.

Build Bazel release artifacts alongside Cargo artifacts openai/codex

by copyberry

Cargo and Bazel build matrices now run on Linux, macOS, and Windows through signing, packaging, and artifact verification. Bazel binaries, packages, and symbols ship under a -bazel suffix while Cargo artifact names stay unchanged, and Python runtime wheels and the Windows installer remain on the Cargo path.

Add an app-server prompt prefix compatibility test openai/codex

by copyberry

The new prompt_prefix_matches_release check compares instructions, tools, and the input preceding the user message against a released CLI, using each binary's bundled model catalog and feature defaults, with response item IDs and transport metadata stripped from the comparison. Any change to the default model-visible prefix has to be gated behind a default-off feature key.

fix(uploads): decode inferred URL filenames safely (#2892) openai/openai-node

by Justin Beckwith

Fetched Responses used to upload filenames like monthly%20notes.txt verbatim; they are now decoded once in the shared filename-inference path so toFile() and multipart uploads both send monthly notes.txt. If decoding would introduce literal %0A, %0D, or %22 multipart escapes, the original encoded basename is preserved to avoid receiver-side double decoding.

fix(deps): refresh development and ecosystem dependencies (#2889) openai/openai-node

by Justin Beckwith

Transitive development and ecosystem dependencies were refreshed to patched releases, including the existing Cloudflare and Vercel overrides, with the SDK API and runtime requirements untouched. The source-map-js 1.2.2 cooldown exception is scoped to that one release; the rest of the desk is routine dependabot bumps of oxfmt and @aws-sdk/credential-provider-node.

Quick answers

What shipped in OpenAI on October 8, 2026?
Codex is standing up a full Bazel release path beside Cargo, while a Guardian fix stops invalidated reviews from being replayed into retries and openai-node repairs how inferred upload filenames are decoded. In total, 53 commits, 68 pull requests, and 4 releases landed.
Who contributed to OpenAI on October 8, 2026?
3 developers shipped this update, including copyberry, Justin Beckwith, and dependabot.
What were the notable OpenAI updates?
Roll back stale Guardian reviews before reusing reviewer history, Add Bazel release staging archives, and Build Bazel release artifacts alongside Cargo artifacts.