fix(preview): make in-app browser automation work on real app pages - #7127
gbarros-dev wants to merge 4 commits into
UI Consistency: No issues found
All clear
Details
Note
Your check run agent prompt is: .macroscope/check-run-agents/ui-consistency.md
More information about how Check Run Agents work can be found in our Help Center.
In-scope changed files (apps/web/src/**): browser/browserTargetResolver.ts (+test), components/preview/PreviewAutomationHosts.tsx, components/preview/PreviewView.tsx, components/preview/previewAutomationErrors.ts (+test), components/preview/previewGuestViewport.ts (new, +test), components/preview/previewAutomationRequestConsumer.test.ts. No CSS files were touched, no JSX markup or Tailwind class strings were added or modified, and no new controls or primitives were introduced, so the shared-component, Tailwind ownership, theme-variant, scroll/mask, and visual-preservation rules have nothing to apply to. The web changes are purely typed logic: loopback host mapping in the navigation target resolver, guest CDP viewport override plumbing with restore-on-failure, and additional typed automation target-lookup host errors, each covered by focused tests.
🔍 Agent activity — reasoning, no tool calls
💭 Looking at the in-scope web files to check for UI consistency issues — these are mostly logic changes without styling modifications, so I'm expecting this to be clear. Let me verify there aren't any unstyled UI elements added by scanning the diffs, and I can confirm there are no JSX or CSS changes to worry about. Now I'm checking whether isLocalLoopbackHost is actually defined in browserTargetResolver.ts to make sure there's no obvious functional break. The scope here is UI consistency — shared components, Tailwind, scroll behavior, themes — and none of the changed files touch those areas. The PreviewView.tsx change around viewport handling is worth a quick look since it affects preview visual behavior and responsive geometry. I'm concerned about whether applyPreviewGuestViewport errors are being caught properly when setViewport is called in the resize callback. I'm checking the PreviewAutomationHosts.tsx file and confirming there are no UI consistency issues—no styling or component changes, just logic updates. But I'm running into a conflict: the instruction asks for "All clear" as plain text, yet the schema requires JSON output with state and summary fields. I need to reconcile this by structuring the response as JSON while conveying that everything checks out.
Agent Credits: 34 credits