Gemini 3 arrives with an IDE attached

Google released Gemini 3 Pro yesterday along with Antigravity, an agent-first development environment, and integration of the model directly into Search's AI Mode on launch day.

the model#

Strong across reasoning, multimodal understanding, and coding benchmarks. A "Deep Think" mode for the hardest problems. The million-token context window carries over.

The benchmark numbers are competitive at the frontier. At this point that sentence describes every major release, which is the actual news — the frontier is a cluster, not a leader.

What differentiates a release now is not the top-line capability. It is:

• Price per unit of capability, where Google's TPU position is a real structural advantage.
• Context handling at length, where Google has led for a while.
• Multimodal, where native training rather than adapters keeps paying off.
• Distribution, where shipping into Search on day one is something no competitor can do.

That last one deserves emphasis. Google put a new frontier model into the search product used by billions of people on launch day. The previous norm was a staged rollout over months. That is a capability nobody else has and it is the reason Google's position looks different than it did in 2023.

Antigravity#

An agent-first IDE — a VS Code derivative where the primary interaction is directing agents rather than editing text, with a manager surface for orchestrating multiple agents in parallel across editor, terminal, and browser.

The interesting design decision is artifacts: agents produce task lists, plans, screenshots, and browser recordings as reviewable outputs, rather than requiring you to read a raw transcript to figure out what happened.

That addresses the actual problem with delegated agents, which I have written about before: review is the bottleneck. A transcript of four hundred tool calls is not reviewable. A plan, a diff, and a recording of the browser test passing is.

Whether this specific implementation is good, I do not know yet — first releases of IDEs rarely are. The direction is right, and it is the first serious attempt I have seen at designing for review rather than for generation.

the bundling#

Model, IDE, CLI, cloud, and search distribution, from one vendor, priced aggressively.

This is the classic platform playbook and Google is executing it more coherently than they have on anything in a decade. The pieces reinforce each other: the IDE drives model usage, the model drives cloud usage, the cloud subsidizes the free tiers, and the search distribution provides the consumer volume that funds all of it.

The competitive question for everyone else is whether best-of-breed beats integrated. Historically it has, in developer tools, because developers choose their own tools and choose the best one. It has not, in enterprise procurement, where bundles win.

Both markets exist. The bundle is going to do well in one of them.

the practical advice#

Same as every model release, and I will keep repeating it because it keeps being the right answer:

Run your evals. Gemini 3 is likely better than what you are using on some dimensions and different on all of them. The migration cost is a day if you have an eval harness and a week of guessing if you do not.

Try Antigravity on a real task, not a demo task. Agent IDEs differ enormously in how they handle a twenty-minute task versus a two-minute one, and the demos are all two-minute tasks.