RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: AI / ML Full archive →

The Wire · Showcase

GPT-5.5 LANDS ACROSS NODE AND PYTHON SDKS, CODEX HARDENS MCP CONFORMANCE

By RepoJournal · Filed · About OpenAI

OpenAI shipped gpt-5.5 model support and tool metadata across both JavaScript and Python SDKs while Codex locked down a full MCP client conformance regression suite to prevent protocol slippage.

The SDK team moved fast on model expansion. Both openai-node v7.4.0 [2] and openai-python v2.53.0 [3] now recognize gpt-5.5 as a valid model across chat, responses, and tool-calling surfaces, with optional name and namespace metadata fields on tool output items [4] [5]. These are backward-compatible additions that let you start targeting the new model without breaking existing code. On the infrastructure side, both Node and Python repos completed their migration off Stainless-owned CI tooling [6] [7], replacing custom release-please triggers with the upstream googleapis action and retiring legacy branch filters, runner selection, and artifact upload helpers. The Python team also fixed a dependency build issue to avoid NumPy source builds that were bloating CI runs. Over in Codex, the real infrastructure story is a conformance regression matrix that runs the Codex executable against a pinned official MCP client conformance suite across shipping, intermediate, and modern protocol versions, plus HTTP and stdio transports and OAuth scenarios [1]. Model instruction consolidation [8] removed the in-memory instruction path and standardized on model_messages for bundled, remote, fallback, and overridden metadata. Linux managed proxy helpers got hardened to detach standard I/O streams, move readiness pipes above the standard descriptor range, and treat zombie processes as exited [9]. The Codex Apps catalog limit jumped from 2,048 to 8,192 items for host-owned registrations while keeping the lower limit for third-party MCP servers [10].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Add MCP client conformance regression gates (#36810) openai/codex
  2. [2] v7.4.0 ↗ openai/openai-node
  3. [3] v2.53.0 ↗ openai/openai-python
  4. [4] feat(api): Add gpt-5.5 model and tool metadata fields (#2049) openai/openai-node
  5. [5] feat(api): Add gpt-5.5 and tool name/namespace to Responses types ↗ openai/openai-python
  6. [6] ci: retire obsolete Stainless infrastructure (#2067) openai/openai-node
  7. [7] ci: migrate release-please to upstream action (#3568) openai/openai-python
  8. [8] Consolidate model instructions in `ModelMessages` (#36787) openai/codex
  9. [9] Harden Linux managed proxy helper lifecycles ↗ openai/codex
  10. [10] Raise the host-owned Codex Apps catalog limit ↗ openai/codex

Quick answers

What shipped in OpenAI on August 4, 2026?
OpenAI shipped gpt-5.5 model support and tool metadata across both JavaScript and Python SDKs while Codex locked down a full MCP client conformance regression suite to prevent protocol slippage. In total, 51 commits, 59 pull requests, and 5 releases landed.
Who contributed to OpenAI on August 4, 2026?
8 developers shipped this update, including thomas, rhan-oai, jif, copyberry, Hayden, Justin Beckwith, github-actions[bot], and Alex Chang.
What were the notable OpenAI updates?
Add MCP client conformance regression gates (#36810), v7.4.0, and v2.53.0.

More from OpenAI

Daily updates, in your inbox

Follow OpenAI

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?