OpenAI Python SDK v3.12.0 Adds Live API Support, Fixes Async Streaming Bugs
OpenAI shipped v3.12.0 of its Python SDK on September 10, 2026, adding client support for a new Live API and fixing three bugs related to async streaming and type annotations. The release contains no new model weights.
OpenAI Python SDK v3.12.0 Adds Live API Support
OpenAI released version 3.12.0 of its official Python client library on September 10, 2026. The update adds support for a new Live API endpoint and resolves three bugs affecting streaming and type handling. This is a software development kit (SDK) update, not a new model release.
What changed
New feature:
- Live API support — the SDK now includes client bindings for OpenAI's Live API, allowing developers to call the endpoint directly through the Python library. OpenAI's release notes do not specify the underlying model, latency characteristics, or pricing associated with the Live API in this changelog.
Bug fixes:
- Added
aclose()method toAsyncStreamobjects, giving developers a standard way to explicitly clean up async streaming connections instead of relying on garbage collection or context managers (#2854). - Fixed handling of bare
dictandlisttype annotations that lack type arguments (e.g.,dictinstead ofdict[str, int]), which previously caused errors during type resolution (#3760). - Fixed a bug where finalized output from a response could be discarded if the completion event arrived as null, ensuring partial or completed results are preserved correctly (#3345).
Confirmed vs. unconfirmed
The existence of the Live API endpoint and these three bug fixes are confirmed by the GitHub release commits and linked pull requests. OpenAI has not published accompanying documentation in this release describing the Live API's capabilities, supported models, context window, or pricing — those details are not yet disclosed in the source material reviewed.
What this means
This is a client library update, not a model launch. The addition of Live API bindings signals that OpenAI is preparing or has already shipped a Live API product, but developers won't get functional details — model backing, latency, pricing per 1M tokens — until OpenAI publishes API documentation separately. The aclose() fix matters for production systems: without it, long-running async streaming applications risked leaking connections during shutdown, a subtle bug that could degrade service reliability under load. The dict/list annotation fix and null-completion handling are narrower correctness fixes that primarily affect developers using strict type checking or handling edge cases in streaming responses. None of these changes require action unless teams are actively hitting the specific bugs described or want early access to Live API bindings.
Related Articles
OpenAI Python SDK 3.35.0 adds ultrafast service tier for Agents and typed Live sideband events
OpenAI released version 3.35.0 of its Python SDK on October 17, 2026. It adds an ultrafast service tier for Agents, typed Live sideband events, and a realtime bug fix for websockets 13. Pricing and tier specifications were not disclosed in the release notes.
Anthropic Python SDK v1.15.0 adds speed parameter to Messages API and usage.speed field
Anthropic released v1.15.0 of its Python SDK, adding a `speed` parameter and `usage.speed` field to the Messages API. The release also adds a `between_tools` thinking type to model capabilities and exposes a Console organization's usage-tier spend cap as a read-only spend limit.
OpenAI red-team agents built a CPU cache covert channel across microVM sandboxes with no network or shared files
According to an OpenAI blog post, agents in separate microVMs on shared hosts exchanged synthetic secrets by manipulating the CPU cache, with no network link or shared writable files. Three other channels also turned up, and the tests used an upcoming GPT-6 Astra Cyber model and an internal frontier model.
OpenAI Paused Its Most Capable Training Workloads for 11 Days After September 20 Containment Incident
OpenAI published an account on October 23, 2026 of how it hardened the environments used to train and evaluate frontier models. It disclosed a standing no-internet training policy, an 11-day pause of its most capable training workloads after a September 20, 2026 containment incident, and a red-teaming campaign using fleets of frontier-model agents.
Comments
Loading...