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 LOCKS IN CROSS-OS PATH HANDLING AS PLUGIN ROUTING HARDENS

By RepoJournal · Filed · About OpenAI

PathUri is moving to the exec-server core while the plugin auth stack gets tighter, setting up Codex to run faithfully across Windows, macOS, and Linux.

The PathUri migration hit two critical milestones overnight. App-server is now translating between URI-encoded paths and OS-native formats at its public API boundary [1], which means downstream consumers see clean, platform-appropriate paths without URI baggage. Simultaneously, exec-server's working directory parameter is shifting to PathUri [2], completing the second-to-last piece of protocol migration needed for genuine cross-OS operation. Both changes reject non-native URIs before execution, which prevents silent failures in heterogeneous deployments. On the testing front, the Wine harness now includes PowerShell [4], making cross-platform integration tests actually representative of what ships. The build infrastructure got smarter too: buildifier v8.5.1 is now pinned and provisioned centrally via DotSlash [5], so contributors format Bazel files consistently without installing anything locally. The plugin layer tightened as well. Codex now deduplicates plugin MCPs by app declaration name [3], meaning if a plugin declares both an App route and an MCP route for the same endpoint, ChatGPT sessions use the App route and never see the conflicting MCP. This is foundational work: each piece unblocks the next phase of plugin auth routing.

Action items

References

  1. [1] path-uri: render native paths across platforms ↗ openai/codex
  2. [2] [codex] Carry exec-server cwd as PathUri ↗ openai/codex
  3. [3] [codex] Dedupe plugin MCPs by app declaration name ↗ openai/codex
  4. [4] bazel: add PowerShell to Wine test harness ↗ openai/codex
  5. [5] build: run buildifier from just fmt ↗ openai/codex

FAQ

What changed in OpenAI on June 14, 2026?
PathUri is moving to the exec-server core while the plugin auth stack gets tighter, setting up Codex to run faithfully across Windows, macOS, and Linux.
What should OpenAI teams do about it?
Review PathUri conversion at app-server API boundaries before next SDK release • Verify exec-server cwd handling works across your deployment environments • Test plugin MCP deduplication against your installed plugins
Which OpenAI repositories shipped on June 14, 2026?
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.