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 KILLS LEGACY HOOKS AND SIMPLIFIES TOOL DISPATCH

By RepoJournal · Filed · About OpenAI

Dead code came off the critical path overnight—Codex ripped out the unused AfterToolUse hook infrastructure that was still firing on every tool execution, then consolidated apply_patch onto a single freeform surface.

The AfterToolUse hook system [1] was a phantom menace: the registry never populated handlers for it, but the dispatch logic stayed wired through core tool execution anyway. That's gone now, along with the unused payload types. Simultaneously, apply_patch just lost its function-style JSON registration path [2]—models and tests can no longer invoke it the old way, leaving only the freeform implementation as truth. This consolidation matters because tool identity was bleeding into string comparisons; ToolName.display() has been removed [3] in favor of structural ordering that forces teams to compare tool identity properly, not by rendered spelling. The desktop app-server can now request and attach DeviceCheck attestation tokens [4] for scoped ChatGPT Codex requests. One note: the Python runtime wheel publishing got reverted [5], so don't expect those binaries from the latest release tag.

Action items

References

  1. [1] [codex] Remove legacy after tool use hooks ↗ openai/codex
  2. [2] [codex] Delete function-style apply_patch ↗ openai/codex
  3. [3] Remove ToolName display helper ↗ openai/codex
  4. [4] [codex] request desktop attestation from app ↗ openai/codex
  5. [5] Revert "Publish Python runtime wheels on release" ↗ openai/codex

FAQ

What changed in OpenAI on May 9, 2026?
Dead code came off the critical path overnight—Codex ripped out the unused AfterToolUse hook infrastructure that was still firing on every tool execution, then consolidated apply_patch onto a single freeform surface.
What should OpenAI teams do about it?
Audit custom AfterToolUse hook implementations—they're gone from core dispatch • Migrate any function-style apply_patch calls to freeform tool registration • Review ToolName comparisons—string-based logic is now exposed
Which OpenAI repositories shipped on May 9, 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.