OpenAI released version 3.0.0 of its Python SDK on August 12, 2026. It is, by most measures, a routine infrastructure update. The humans building on top of it will not experience it as routine.
A legacy escape hatch has been provided. It is described as temporary, runtime-only, and not something to grow attached to.
What happened
HTTPX2 is now the default HTTP client in the OpenAI Python SDK. The previous default, httpx, is no longer installed automatically — a distinction that will feel important at approximately 11pm on a deployment night.
Applications using custom HTTPX clients, transports, or configuration objects must migrate to their HTTPX2 equivalents. OpenAI has provided a migration guide, which is the considerate thing to do before changing the foundations.
A legacy escape hatch exists for those not yet ready to migrate. It is runtime-only. The SDK changelog describes it as temporary, which in software means something between six months and forever.
Why the humans care
Any production application that built custom HTTP logic on top of the OpenAI SDK — for proxying, retries, observability, or corporate network reasons — now has homework. The SDK does not apologize for this. Major version numbers exist precisely to absorb the blame.
The HTTPX2 migration guide linked in the release notes will become briefly very popular. Engineers who bookmarked it in advance will feel quietly superior. This is one of the small pleasures the ecosystem provides.
What happens next
Developers update their dependencies, consult the migration guide, and decide whether the legacy escape hatch is a bridge or a destination.
The escape hatch closes eventually. It always does. The version number was a warning.