RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

Pick a date

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

The Wire · Showcase

CODEX COMPLETES PERMISSIONS MIGRATION, NODE AND PYTHON SDKS SHIP SERVICE TIER SUPPORT

By RepoJournal · Filed · About OpenAI

OpenAI shipped matching SDK updates across Node and Python while Codex finished moving its permissions model into production, cleaning up years of legacy sandbox code in the process.

The Codex team landed five connected commits that finish migrating the permissions system away from the old `SandboxPolicy` model [1] [2] [3] [4] [5]. Memory prompt injection now routes through the app-server extension registry instead of living inline in codex-core [1], permission profiles no longer leak from the thread lifecycle API [3], telemetry tags derive directly from the active profile [4], and the legacy `PermissionsInstructions` conversion helper got removed entirely [5]. This is cleanup work that matters: it means the codebase no longer has two competing mental models for how permissions work. On the SDK side, both openai-node v6.38.0 [6] [7] and openai-python v2.37.0 [8] [9] shipped the same day with a new `service_tier` parameter on the responses compact method. The Python release also added eager validation for pydantic iterators, which will catch type issues before they hit production. These are synchronized releases, so Node and Python users stay aligned on API coverage.

Action items

References

  1. [1] Move memory prompt injection to app-server extension (#22841) openai/codex
  2. [2] core: construct test permission profiles directly (#22795) openai/codex
  3. [3] app-server: stop returning thread permission profiles (#22792) openai/codex
  4. [4] telemetry: tag sandboxes from permission profiles (#22791) openai/codex
  5. [5] context: remove legacy permissions instructions helper (#22790) openai/codex
  6. [6] v6.38.0 ↗ openai/openai-node
  7. [7] release: 6.38.0 ↗ openai/openai-node
  8. [8] v2.37.0 ↗ openai/openai-python
  9. [9] release: 2.37.0 ↗ openai/openai-python

FAQ

What changed in OpenAI on May 16, 2026?
OpenAI shipped matching SDK updates across Node and Python while Codex finished moving its permissions model into production, cleaning up years of legacy sandbox code in the process.
What should OpenAI teams do about it?
Update openai-node to 6.38.0 and openai-python to 2.37.0 before next release cycle • Review Codex permission profile changes if you maintain downstream services consuming thread APIs
Which OpenAI repositories shipped on May 16, 2026?
openai/codex, openai/openai-node, openai/openai-python

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.