$ the-wire · showcase
Codex drops Bazel from CI and release artifacts
By RepoJournal · Filed · About OpenAI · Composed from the cited sources · methodology
Codex moved its build and release matrices to Cargo only after the BuildBuddy key was revoked, while the SDKs kept hardening the Responses and Realtime WebSocket paths.
Make Bazel checks advisory and pause Bazel release artifacts (#58717) openai/codex
With the BuildBuddy key revoked, Bazel is out of the blocking-ci required dependencies and the Bazel-backed argument comment lint and SDK jobs are advisory, so Bazel failures no longer block Rust CI. Release build and packaging matrices are restricted to Cargo, Windows included, so no Bazel-backed artifact ships.
Remove Bazel outputs from DotSlash release configs (#58757) openai/codex
The DotSlash release configs no longer reference Bazel outputs for Codex, the Windows command runner and sandbox setup, or provisioned macOS packages, because those assets are absent from the Cargo-only fixture for 0.167.0-alpha.2. Regression tests now fail when a configured output has no matching asset.
feat(responses): add WebSocket lane overflow isolation openai/openai-python
The new isolate_lane_overflow=True option on the sync and async Responses WebSocket session constructors keeps healthy lanes on the same connection when one lane's event queue fills; the default stays False, where a slow lane still closes the managed session. Failed lanes discard queued events and collected response state, and their IDs stay reserved until reconnect.
feat(responses): retain sparse WebSocket output facts openai/openai-node
Caller-fed WebSocket deltas that arrive before their output items used to mark the stream unavailable; the go-openai-node accumulator now retains received text, refusal, function and custom-tool input and MCP arguments in an optional partialOutput view, preserving wire indices and leaving missing item metadata absent.
feat(responses): accumulate rich WebSocket progress openai/openai-python
ResponsesWebSocketAccumulator now tracks reasoning, shell, interpreter and tool status progress plus queued response metadata, exposed through detailed_snapshot() with terminal responses still authoritative. In the same stretch, the Realtime clients reject bare workload-identity and Bedrock profiles before connecting and route stable and beta Responses WebSockets through SDK-owned connection he...
