Chrome 146 Finally Lets AI Control Your Real Browser — Google OAuth Included

I asked Claude Code to pull model ratings from CivitAI. Simple enough request. The AI opened a fresh Chrome window. Blank slate. No cookies. No session. Navigated to CivitAI — and hit the Google login button. It was stuck. Google intentionally blocks OAuth flows from automated browser instances. That's correct behavior from a security standpoint. But for AI browser automation, it was a hard wall. Chrome 146 just knocked that wall down. The Root Problem: AI Was Working in an Empty House Before Chrome 146, the chrome-devtools-mcp server launched Chrome with --user-data-dir pointing to a separate, isolated profile. That separate profile had nothing in it. No cookies. No saved passwords. No active sessions. Every site you'd ever logged into — GitHub, Google Analytics, CivitAI — required manual re-login every single time. And for Google OAuth specifically, manual re-login wasn't even an option. Google detects the automated browser fingerprint and blocks the flow outright. Chrome 136 Made Th