Skip to main content
The most reliable options are a saved profile or a human checkpoint.

Reuse a logged-in profile

Sync your local login, then load that profile in the run:
This avoids another 2FA challenge while the site’s cookies remain valid.

Let a human take over

Ask the first run to stop at the 2FA screen, get its live_view_url from the browser.ready event, and have the user enter the code. Set keepAlive on the first run so the browser stays open while the user works (typed in SDK 3.12+); without it, the browser stops about 2 minutes after the run ends. The follow-up inherits the value, and kept time is billed. Then continue with the same session:
See Human in the loop for retrieving and embedding the live browser URL. Never put passwords or TOTP secrets directly in a prompt.