Consider migrating the Python SDK from httpx to httpx2 #200

Request

Would you consider migrating the Python SDK from httpx to httpx2, or share whether this is already planned?

The SDK currently requires httpx>=0.23.0,<1. We'd like to standardize on httpx2, but Browserbase still requires the original client stack.

Maintenance activity

As of 2026-10-13, HTTPX's latest release is 0.28.1, published on 2024-12-06, and its latest commit is dated 2026-02-23. Development and releases have slowed substantially.

Pydantic describes httpx2 as a maintained continuation of HTTPX, intended to provide ongoing maintenance and timely security updates. This makes it a useful path forward for applications and SDKs relying on this transport.

Ecosystem migrations

Several projects have already adopted httpx2:

• OpenAI Python SDK: migrate to HTTPX2, merged on 2026-08-12.
• MCP Python SDK: replace httpx and httpx-sse with httpx2, merged on 2026-07-14.
• Starlette: support httpx2 in TestClient, merged on 2026-05-25, preferring httpx2 while retaining an httpx fallback.

Migration considerations

The httpx2 migration guide describes a largely compatible public API, but clients and exceptions are distinct types. It also documents the switch to the system certificate trust store, changed logger names and User-Agent, and the Python 3.10 minimum. Browserbase currently supports Python 3.9, so the supported Python versions and release strategy need consideration.

Since this SDK is generated with Stainless, does adopting httpx2 require a shared runtime or generator update? A supported migration path or an indication of the planned timeline would help downstream applications coordinate their own migration.