CDP flow does not support standard HTTP redirects (301/302) unlike Playwright

[Ishita-Jinturkar]

Currently, when using the browser-use CDP flow, HTTP redirects (e.g., 301, 302) are not handled in the same way as in Playwright.

In Playwright, standard redirect flows are supported out of the box, the client request follows the redirect and continues execution seamlessly. However, with browser-use via CDP, the redirect handling seems missing or inconsistent. This creates issues when working with authentication or proxy-based setups where redirect-based flows are common.

Expectations:

• Redirects (301, 302, etc.) should be followed automatically in the CDP flow, just like in Playwright.

• The client should not need to manually handle redirect logic.

Use Case / Impact:

• This affects integration scenarios where authentication relies on redirect chains.

• Playwright currently works fine with the same setup, but the CDP path in browser-use breaks due to lack of redirect support.