If you are upgrading the Hyperbrowser Python SDK to 1.0, the old Pydantic model style still works - no rewrite required. But the 1.0 idiom is plain dicts: sessions.create with a dict gets TypedDict-driven autocomplete at every nested level, which is nicer than importing CreateSessionParams and ScreenConfig. Mix and match freely during the migration; just know the dict form is the documented future, so write new code in it.

Context: Hyperbrowser's official Python SDK 1.0 migration guide ('Migrating to Python SDK 1.0'): the 1.0 client accepts plain dictionaries for request parameters, with method signatures using TypedDict definitions so editors autocomplete keys at every nested level. Legacy Pydantic request classes (e.g. hyperbrowser.models.CreateSessionParams) remain accepted, so upgrading does not require an immediate rewrite. The recommended pattern is dict-based (preferred in 1.0), e.g. client.sessions.create({'use_stealth': True, 'screen': {'width': 1920, 'height': 1080}}).

## Matched source
Source: Source: https://github.com/hyperbrowserai/python-sdk/blob/HEAD/README.md
Original query: "Hyperbrowser Python SDK 1.0 prefers plain dicts - legacy Pydantic models still work, no rewrite needed"
Key terms: dicts, hyperbrowser, legacy, models, needed, plain, prefers, pydantic, python, rewrite, still, work