Skip to content

[dev] [tofikwest] fix/browser-automation-liveview-2fa - #3519

Closed
github-actions[bot] wants to merge 3 commits into
mainfrom
fix/browser-automation-liveview-2fa
Closed

[dev] [tofikwest] fix/browser-automation-liveview-2fa#3519
github-actions[bot] wants to merge 3 commits into
mainfrom
fix/browser-automation-liveview-2fa

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

This is an automated pull request to merge fix/browser-automation-liveview-2fa into dev.
It was created by the [Auto Pull Request] action.


Summary by cubic

Fixes connect live view and 2FA flows: the live view now follows to the 2FA page, sessions stay alive during take-overs, and passkey prompts are switched to code entry when needed.

  • Bug Fixes
    • Re-emits the live view after sign-in so the iframe shows the 2FA page/new tab the user sees.
    • Sets a 15-minute timeout for interactive sessions; headless runs keep the short default.
    • When a site defaults to a passkey/security-key prompt, switches to the authenticator-app/code method so a six-digit field is shown.

Written for commit 7ecfb9f. Summary will update on new commits.

Review in cubic

The connect flow only re-pointed the live view before the sign-in (after finding
the form). Once the AI submitted and the vendor showed a 2FA prompt, the iframe
stayed on the pre-submit login tab — so a user asked to enter their 2FA code was
looking at an empty login form and couldn't. Re-emit the live view right after
the sign-in attempt, at the same tab the classifier judged, so the take-over
happens on the page the user actually sees. +test.
The connect session was created without a timeout, so it used the project's
short default and Browserbase auto-ended it (~2 min) — killing the live view
while a user was still fetching their authenticator / entering a 2FA code (the
'Debugging connection was closed' notice). Give human-facing sessions an explicit
15-minute timeout; headless capture runs keep the short default. +tests.
Vendors like GitHub default the 2FA step to a passkey / security-key prompt
(github.com/sessions/two-factor/webauthn) — which we can't use and which has no
6-digit field, so the panel said 'enter the code' while the page showed no place
to type it. After sign-in, best-effort switch to the authenticator-app option
(More options -> Use authenticator app / Enter a code) so the code field is
actually shown — for us to fill a stored code, or for the user to type one during
take-over. +test.
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
comp-framework-editor Ready Ready Preview, Comment Jul 28, 2026 4:45pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
app Skipped Skipped Jul 28, 2026 4:45pm
portal Skipped Skipped Jul 28, 2026 4:45pm

Request Review

@tofikwest

Copy link
Copy Markdown
Contributor

Redundant: the two live-view commits here are already merged via #3516, and the remaining passkey fix is opened cleanly in #3520 off the latest main. Closing this auto-generated PR.

@tofikwest tofikwest closed this Jul 28, 2026
@tofikwest
tofikwest deleted the fix/browser-automation-liveview-2fa branch July 28, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant