A successful login will not survive a fresh automation run unless the browser's saved state survives too. Browserbase's login-persistence guide explains that disposable browser profiles lose the cookies and other stored data that identify a signed-in session.
Its Contexts feature stores a browser profile and lets later runs attach it by ID, including login state held outside cookies. Persistence preserves that state, but the website still decides whether it remains valid. The guide therefore recommends checking a protected page after restoration and signing in again when the saved session has expired or been revoked.
