RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

Keep up with OpenAI in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: AI / ML Full archive →

The Wire · Showcase

CODEX HARDENS APP-SERVER INTEGRATION AND TIGHTENS ADMIN CONTROLS

By RepoJournal · Filed · About OpenAI

Codex shipped deterministic integration tests that prove the SDK, app-server runtime, and public clients work together end-to-end, plus three security and capability wins for managed deployments.

The SDK integration harness [1] closes a critical testing gap — behavioral tests could catch wrapper mistakes, but they never validated that the pinned app-server process, request routing, and sync/async clients actually worked together in production. This PR starts the real app-server and mocks only at the HTTP boundary, giving you the confidence that SDK changes won't break at runtime. On the capability side, auth elicitation now advertises itself properly [2] when enabled behind the feature flag, ensuring backward compatibility and giving servers explicit signal before they send elicitations. Admins got the tool approval win they needed: managed requirements can now enforce per-tool approval rules centrally [3], closing the gap where only normal config could express those constraints. Security-critical: managed filesystem deny-read restrictions now survive escalation paths [4] — explicit escalations, prefix-rule allows, and sandbox-denial retries can no longer rebuild the runtime policy and expose paths an administrator locked down. On the client side, remote iOS and Android clients no longer bloat `thread/resume` responses with MCP tool call payloads and image-generation results [5]; this is a temporary redaction layer while the team builds toward paginated SQLite-backed APIs.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [7/8] Add Python SDK app-server integration harness (#22014) openai/codex
  2. [2] [elicitation] Advertise new url elicitation capability when auth_elicitation is enabled. ↗ openai/codex
  3. [3] feat(connectors): support managed app tool approval requirements ↗ openai/codex
  4. [4] fix(permissions): preserve managed deny-read during escalation ↗ openai/codex
  5. [5] fix(app-server): thread history redaction for remote clients ↗ openai/codex

Quick answers

What shipped in OpenAI on May 12, 2026?
Codex shipped deterministic integration tests that prove the SDK, app-server runtime, and public clients work together end-to-end, plus three security and capability wins for managed deployments. In total, 50 commits, 50 pull requests, and 3 releases landed.
Who contributed to OpenAI on May 12, 2026?
3 developers shipped this update, including mzeng-openai, viyatb-oai, and owenlin0.
What were the notable OpenAI updates?
[7/8] Add Python SDK app-server integration harness (#22014), [elicitation] Advertise new url elicitation capability when auth_elicitation is enabled, and feat(connectors): support managed app tool approval requirements.

More from OpenAI

Daily updates, in your inbox

Follow OpenAI

Keep up with OpenAI in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?