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 CONSOLIDATES TOOL CALL OWNERSHIP INTO CORE TURNITEM

By RepoJournal · Filed · About OpenAI

McpToolCall migrations are complete — app-server now emits tool calls as canonical turn items instead of synthesizing them from deprecated legacy events, collapsing three separate changes into a unified dispatch and response model.

MCP tool calls moved into core `TurnItem`s [1], closing the gap between app-server synthesis and v2 `ThreadItem::McpToolCall` shape. This keeps MCP result semantics in one place instead of spread across conversion code, and gives core ownership over the lifecycle — it now decides whether a completed call is `completed` or `failed`. Simultaneously, app-server dispatch refactored response sending [2]: normal `ClientResponsePayload` sends centralized in the dispatch path, while explicit-response methods stay explicit where they need custom ordering or delayed delivery. This unwinds handler wrappers that were making it impossible to see which requests return payloads and which emit notifications after response. On the documentation front [3], local-only docs and planning specs are being removed from the repository — `docs/` now links to the canonical surface on developers.openai.com instead of duplicating transient implementation notes.

Action items

References

  1. [1] [codex] Emit MCP tool calls as turn items ↗ openai/codex
  2. [2] [codex] Refactor app-server dispatch result flow ↗ openai/codex
  3. [3] Remove local docs and specs ↗ openai/codex

FAQ

What changed in OpenAI on May 4, 2026?
McpToolCall migrations are complete — app-server now emits tool calls as canonical turn items instead of synthesizing them from deprecated legacy events, collapsing three separate changes into a unified dispatch and response model.
What should OpenAI teams do about it?
Review dispatch flow changes in your MCP integrations — response ordering may have shifted • Update local tooling pointing to docs/ — redirect to developers.openai.com
Which OpenAI repositories shipped on May 4, 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.