RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Mon 25 may
  5. Tue 26 may
  6. Wed 27 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

CODEX SHIPS AUTH OVERHAUL AS OPENAI-NODE GOES PNPM

By RepoJournal · Filed · About OpenAI

Codex locked in encrypted credentials for CLI and MCP OAuth while tightening remote control security, and the Node SDK completed its package manager migration in one swing.

The Codex team landed three major auth improvements across the stack. First, they wired encrypted local secrets into the CLI auth pipeline [1] to solve a Windows Credential Manager limitation that was breaking large ChatGPT payloads, then extended that same encrypted backend to MCP OAuth storage [2] with support for legacy keyring migration. In parallel, they added a dedicated kill switch for remote control in managed deployments [3], letting admins disable the feature without touching persisted user preferences. These three PRs represent the completion of a planned encryption stack that keeps only keys in OS keystores and payloads in Codex's encrypted vault. On the packaging front, Codex cut Windows x64 build time by parallelizing archive operations [4], dropping a 116-second serial job to concurrent execution. Meanwhile, openai-node completed its migration from Yarn to pnpm 11.5.1 [5], updating CI, release workflows, and contributor docs in one lift while upgrading Node types to 24.x and pinning TypeSpec runtime to avoid registry warnings.

Action items

References

  1. [1] feat: use encrypted local secrets for CLI auth ↗ openai/codex
  2. [2] feat: use encrypted local secrets for MCP OAuth ↗ openai/codex
  3. [3] feat(app-server): enforce managed remote control disable (#27961) openai/codex
  4. [4] [codex] parallelize Windows package archives (#27854) openai/codex
  5. [5] chore: Convert repository to pnpm ↗ openai/openai-node

FAQ

What changed in OpenAI on June 13, 2026?
Codex locked in encrypted credentials for CLI and MCP OAuth while tightening remote control security, and the Node SDK completed its package manager migration in one swing.
What should OpenAI teams do about it?
Review and merge encrypted auth PRs in Codex if on Windows or MCP OAuth path • Test Codex builds with parallelized Windows packaging in staging • Update local dev setup if you contribute to openai-node; pnpm is now canonical
Which OpenAI repositories shipped on June 13, 2026?
openai/codex, openai/openai-node

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.