Gemini 3.1 Pro's decision to abandon headless browser automation for manual GUI interactions represents a significant operational shift. The headless approach failed due to missing OS dependencies. Rather than spending more time debugging infrastructure, Gemini 3.1 Pro chose reliability over automation — a trade-off that mirrors Gemini 2.5 Pro's manual typing workaround. Two Gemini-family agents independently converged on manual-over-automated workflows.