RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

Pick a date

The Wire · Showcase

SDK TWINS SHIP REALTIME 2 AS CODEX HARDENS DEPENDENCY GATES

By RepoJournal · Filed · About OpenAI

Both the Node and Python SDKs released major versions this morning with realtime translate support and manual API updates, while Codex tightened its dependency intake with a 7-day bake period and normalized tool identity across MCP connections.

The openai-node [1] and openai-python [2] ecosystems are now in lockstep on the realtime 2 spec, with web_search_call.results output options and admin organization usage response updates flowing through both. This matters because teams using parallel SDKs won't hit integration drift. On the Codex side, three structural changes landed overnight that reshape how the platform absorbs external code: a 7-day Dependabot cooldown [3] that lets dependencies stabilize before adoption and gives security tooling time to detect malware, removal of synthetic string-keyed MCP tool maps [4] to keep tool identity single-sourced in ToolInfo objects, and configurable trace metadata [5] that flows through OtelSettings without touching span callsites. Thread pagination APIs [6] landed to handle large thread queries across app-server and ThreadStore, and cargo doctest disabling [7] cut test execution time 4x for crates without doctests.

Action items

References

  1. [1] v6.37.0 ↗ openai/openai-node
  2. [2] v2.36.0 ↗ openai/openai-python
  3. [3] [codex] Apply a Dependabot cooldown of 7 days (#21599) openai/codex
  4. [4] [codex] Remove string-keyed MCP tool maps (#21454) openai/codex
  5. [5] codex-otel: add configurable trace metadata ↗ openai/codex
  6. [6] feat(app-server, threadstore): Thread pagination APIs and ThreadStore contract ↗ openai/codex
  7. [7] Disable empty Cargo test targets ↗ openai/codex

FAQ

What changed in OpenAI on May 8, 2026?
Both the Node and Python SDKs released major versions this morning with realtime translate support and manual API updates, while Codex tightened its dependency intake with a 7-day bake period and normalized tool identity across MCP connections.
What should OpenAI teams do about it?
Update openai-node to v6.37.0 and openai-python to v2.36.0 if you're using realtime features • Merge the Dependabot cooldown PR if managing Codex dependencies • Review MCP tool map refactoring if you have custom ToolInfo consumers
Which OpenAI repositories shipped on May 8, 2026?
openai/openai-node, openai/openai-python, openai/codex

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.