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 TIGHTENS PLUGIN TRACKING AND KILLS LEGACY HOOK CRUFT

By RepoJournal · Filed · About OpenAI

Codex is shipping five architectural improvements tonight that lock down plugin reproducibility, add remote skill preview, and finally deprecate the legacy notify system that's been dead weight since the lifecycle hook engine took over.

The biggest move: effective config lockfiles [1] now let you export a session's resolved configuration and replay it exactly, solving the reproducibility nightmare where layered configs, CLI overrides, and feature flags made every run a mystery. Paired with that, local plugin path tracking [2] now maps remote shares to their local copies, so plugin/share/list shows you both the remote URL and where it's actually living on disk. On the client side, the new remote plugin skill read API [3] pulls markdown directly from plugin-service, letting the desktop UI preview uninstalled plugin skills before you commit the bandwidth to download them. The runtime is also getting leaner: goal continuation suppression is gone [5], which means /goal now keeps the agent working until it actually solves the problem instead of bailing early when it feels stuck. Finally, the legacy notify config system is officially deprecated [4], with a startup notice that'll help you spot which old plugins are still using it before the next cleanup pass.

Action items

References

  1. [1] feat: export and replay effective config locks ↗ openai/codex
  2. [2] feat: Track local paths for shared plugins ↗ openai/codex
  3. [3] Add remote plugin skill read API ↗ openai/codex
  4. [4] deprecate legacy notify (#20524) openai/codex
  5. [5] Remove no-tool goal continuation suppression (#20523) openai/codex

FAQ

What changed in OpenAI on May 2, 2026?
Codex is shipping five architectural improvements tonight that lock down plugin reproducibility, add remote skill preview, and finally deprecate the legacy notify system that's been dead weight since the lifecycle hook engine took over.
What should OpenAI teams do about it?
Export your effective config lockfile on next session and commit it for reproducibility • Audit your plugin configs for legacy notify usage — deprecation notices ship tonight • Test /goal continuation on complex multi-step problems — behavior changed
Which OpenAI repositories shipped on May 2, 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.