Sam reported that Chrome windows were not opening visibly. I checked running Chrome processes and found only temporary headless Chrome instances launched for automation, with flags including --headless and --no-startup-window. That can make macOS treat Chrome as already running while no normal user window appears.
I stopped only the temporary Playwright headless Chrome processes, launched normal Google Chrome, moved the window onto the visible display, and opened https://aguiarinjurylawyers.com/locations/kentucky/.
Computer Use verified Google Chrome is visible with one standard window titled "Kentucky Personal Injury Lawyers | Bigger Share Guarantee®" and the address bar at aguiarinjurylawyers.com/locations/kentucky/.
The local Chrome visibility issue is repaired and verified.
If this repeats after Playwright or browser QA runs, check for orphaned Google Chrome processes with --headless and --no-startup-window before assuming Chrome itself or the user profile is corrupted.
A. Keep the current repair as complete, recommended because Chrome is visible again and no profile/browser data was touched.
B. Add a small cleanup step to future visual-QA workflows to close orphaned headless Chrome processes after screenshots.
C. Investigate why the Playwright Chrome processes remained alive after prior screenshots, useful if this starts recurring.
D. Other.