Faster cheaper models change how browser based coding agents feel
The loud headline from I/O is that Gemini 3.5 Flash beats the old 3.1 Pro on a bunch of tasks while being cheaper and much faster.
The quieter implication is that agent loops get cheaper.
If a model is good enough and fast enough, you stop treating an agent run like one precious attempt. You can retry, run a verifier, ask for a narrower patch, test a second approach, or keep a lightweight background agent alive without feeling like every token is a luxury purchase.
That is why browser based coding environments should care. Dynamic subagents, scheduled tasks, cloud based runs, Replit style workspaces. The model is not just a better autocomplete engine. It is becoming execution infrastructure.
I have been testing browser IDEs, Gemini CLI, Claude Code and Verdent on small repo tasks. The frustrating failures are rarely "the model was dumb." More often it is context getting messy, tool calls drifting, or the final diff being too large to trust.
A fast Flash model helps, but the system around the model decides whether the run is usable. That is the part I am watching.