Fix v3 KYC lookup with validated registry cell reads - #109
Draft
shrey150 wants to merge 1 commit into
Draft
Conversation
shrey150
marked this pull request as draft
September 11, 2026 19:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft — not the CUA-preserving fix. This implementation restores lookup output by removing CUA. The template is intended to demonstrate CUA, so this is an alternative workaround, not a complete fix for the intended behavior. It is held as draft while the provider-authentication gap is investigated.
The KYC template fails in Playground after opening the SF business registry: its Google computer-use request gets HTTP 403 because the sandbox provides Browserbase credentials and the hosted CUA path does not supply Google credentials. The template then logs
Error during business lookup: {}.Replace CUA with Stagehand v3 browser locators and direct reads of the registry's labeled cells. The flow selects the actual DBA checkbox, waits for a single matching record, reads both sides of the virtualized grid, and preserves published blanks as
null. It makes no model calls, reports meaningful errors, and awaits completion before closing the session. The README now describes this flow and its Browserbase-only credential requirement.This PR targets production, the v3 source branch. Core PR #12059 ships the generated Playground asset and points regeneration at this branch. Merge this source change first so later core regeneration preserves the fix.
E2E verification
{}console error.null. Session released.49544db67ad694477b787ac0875ebb5c5bff1066a37c4976a135b3d9d8ab7afc.The local UI test uses actual Playground components, constructor transformation, EvalContext, runner HTTP/SSE server, and BrowserbaseEvents with real Browserbase sessions. Auth/navigation and Vercel provisioning surroundings are substituted locally; it does not verify deployed authentication or Vercel VM provisioning. The public dataset API was used only as an independent test oracle; the template performs the lookup in the browser.
This fixes KYC. Other template defects found during the incident are outside this PR.