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

X.509 Workload Identity Lands in openai-node

By RepoJournal · Filed · About OpenAI

Part 3 of 5 is live, and OpenAIs Node SDK just got its most significant auth upgrade in years.

The openai-node SDK is rolling out pinned X.509 workload identity, with three parts of a five-part stack merged overnight [1][2][3]. Part 1 adds certificate-authenticated OAuth exchange against the single approved mtls.auth.openai.com issuer [1], while Part 2 introduces a frozen transport capability registry shared across CJS and ESM [2]. Part 3 wires it all into the client, pinning the global mTLS API origin and excluding Azure, Bedrock, and custom dispatchers [3]. Expect breaking changes as this matures. Across the stack, Codex hardened managed worktrees with thread ownership metadata and atomic no-clobber writes [4], and sanitized Git remote credentials before they enter thread and turn metadata [5]. "Git remote URLs can embed usernames, passwords, or tokens," notes the Codex PR [5]. openai-python also gained generated request encoding for Realtime WebRTC setup [6] and project residency config with deprecated geography [7]. The Node SDK broke ecosystem CLI checks to run on Windows [8] and fixed Castiron checks for external-fork PRs [9]. Codex added an explicit remote executor connection refresh for planned replacement [10] and tracks image generation request IDs in analytics [11], while moving relay test helpers into shared support [12].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] feat(auth): add pinned X.509 workload token exchange (#2470) openai/openai-node
  2. [2] feat(auth): attest cross-module X.509 transport capabilities (#2471) openai/openai-node
  3. [3] feat(auth): integrate attested X.509 workload identity into clients (#2472) openai/openai-node
  4. [4] Add thread ownership metadata for managed worktrees ↗ openai/codex
  5. [5] Sanitize credentials from Git remote metadata ↗ openai/codex
  6. [6] fix(api): encode Realtime call offers and session configuration ↗ openai/openai-python
  7. [7] feat(api): add project residency configuration and cost quantity units ↗ openai/openai-python
  8. [8] test: make ecosystem CLI checks portable on Windows (#2431) openai/openai-node
  9. [9] fix: publish Castiron checks for external-fork pull requests (#2464) openai/openai-node
  10. [10] Add explicit remote executor connection refresh ↗ openai/codex
  11. [11] Track image generation request IDs in analytics ↗ openai/codex
  12. [12] Move relay helpers into exec-server test support ↗ openai/codex

Quick answers

What shipped in OpenAI on August 26, 2026?
Part 3 of 5 is live, and OpenAIs Node SDK just got its most significant auth upgrade in years. In total, 62 commits, 71 pull requests, and 3 releases landed.
Who contributed to OpenAI on August 26, 2026?
5 developers shipped this update, including copyberry, george, Hayden, Justin Beckwith, and apcha-oai.
What were the notable OpenAI updates?
feat(auth): add pinned X.509 workload token exchange (#2470), feat(auth): attest cross-module X.509 transport capabilities (#2471), and feat(auth): integrate attested X.509 workload identity into clients (#2472).

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?