The Wire · Showcase
CODEX TIGHTENS THREAD CLASSIFICATION, NODE SDK ADDS X.509 TRANSPORT
By RepoJournal · Filed · About OpenAI
Codex now requires content classification for all thread sources and extension fragments, while the Node SDK introduces caller-attested X.509 transport for hardened auth flows.
Codex shipped five commits hardening thread and fragment handling across its execution layer [1][2][3][4][5]. The most significant change requires all extension prompt fragments and contextual user fragments to declare a stable ContentItemKind, enforcing producer ownership of content classification at the API boundary [3][5]. A new global `codex exec --thread-source` option lets callers tag newly created and forked threads, defaulting to `user` when omitted and exposing the classification as `threadSource` in the TypeScript SDK [1]. The system now properly shuts down resumed descendants when archiving parent thread trees, fixing a bug where collaboration could resurrect archived threads without unarchiving their rollout [4]. Patch approval paging now has full regression coverage for live and replayed approvals recovering their file changes, with verification for scrolling, resizing, and accepting or canceling requests exactly once [2]. In parallel, the Node SDK added a preview `openai/auth/x509-transport` entrypoint for caller-attested X.509 transport using Undici Agent or ProxyAgent, with private branding and runtime validation to prevent unsupported configurations and per-request dispatcher replacement [6][7]. Undici remains optional for ordinary SDK consumers.
One email a day. Unsubscribe in one click.
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. Read a past issue →
Action items
- → Update extension code to provide ContentItemKind for all prompt and contextual fragments openai/codex [plan]
- → Review thread source classification in CLI callers and update TypeScript SDK integrations openai/codex [plan]
- → Evaluate X.509 transport preview for hardened auth scenarios, verify Undici compatibility openai/openai-node [monitor]
References
- [1] Allow exec callers to classify new threads ↗ openai/codex
- [2] Add regression coverage for patch approval paging ↗ openai/codex
- [3] Require content kinds for extension prompt fragments ↗ openai/codex
- [4] Shut down resumed descendants when archiving thread trees ↗ openai/codex
- [5] Classify contextual fragments with content kinds ↗ openai/codex
- [6] feat(auth): add caller-attested X.509 transport capability (#2428) openai/openai-node
- [7] feat(auth): add caller-attested X.509 transport capability ↗ openai/openai-node