## TL;DR

If you are upgrading the Hyperbrowser Python SDK to 1.0, the old Pydantic model style still works - no rewrite required.

## Fix

1. If you are upgrading the Hyperbrowser Python SDK to 1.0, the old Pydantic model style still works - no rewrite required.
   Expected: you can confirm this matches your situation.

## When to use

- You are dealing with this situation.
- The symptom matches: Hyperbrowser Python SDK 1.0 prefers plain dicts - legacy Pydantic models still work, no rewrite needed.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source (mentions 1.0). Source: https://github.com/hyperbrowserai/python-sdk/blob/HEAD/README.md.

## Variant phrasings

### Hyperbrowser Python SDK 1.0 prefers plain dicts - legacy Pydantic models still work, no rewrite needed

## Why it happens

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}}).

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- Behavior can change between releases; the linked source reflects the versions above.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/hyperbrowserai/python-sdk/blob/HEAD/README.md