Google Rebuilds Antigravity 2.0 Around Gemini 3.5 Flash to Replace Coding With Orchestration

Google used its I/O 2026 developer keynote to make a pointed argument: the era of AI-assisted coding is over. The era of AI-agentic coding has begun. The announcements were not a single model drop or a feature update , they were a coordinated stack, from model to IDE to browser standard, designed to move the unit of developer work from a prompt to an autonomous workflow.

The engine: Gemini 3.5 Flash

At I/O 2026, Google launched Gemini 3.5 Flash, combining frontier intelligence with speed. It outperforms Gemini 3.1 Pro across almost all benchmarks while running four times faster than other frontier models, providing the high-speed engine needed for real-world agentic workflows. That speed gap matters more than it sounds. In agent loops, every reasoning step, every tool call, every synthesis pass costs latency. A 4x speed advantage compounds across dozens of turns in a single task.

Gemini 3.5 Flash is priced at $1.50/MTok input and $9.00/MTok output. Compare that to Claude Opus 4.7 at $15/$75 per MTok , that's 10x cheaper on input. For coding agents that make many small calls , writing tests, fixing linting errors, generating boilerplate , Gemini 3.5 Flash's price point starts to look compelling.

The platform: Antigravity 2.0

The 2.0 release is a complete rebuild. Gone is the VS Code fork that defined Antigravity 1.0. In its place: a standalone desktop app for multi-agent orchestration, a Go-based CLI that replaces the Gemini CLI entirely, an SDK for self-hosted agent deployment, and Managed Agents in the Gemini API that give you an autonomous coding agent with a single API call.

The headline capability is parallel subagent orchestration , a concept worth unpacking. Rather than a single agent working through a task sequentially, you hand the main agent a complex task like "refactor our auth module, update the corresponding tests, and document the API changes." The primary agent breaks that task into components, spawns subagents for the test update and documentation pieces, and those subagents run asynchronously in isolated contexts. The main conversation thread does not stall while subagents work. You get notified when they complete, and their outputs come back into your primary thread as structured results.

Here is a conceptual look at what orchestrating those subagents via the SDK looks like:

import { AgentOrchestrator } from '@google/antigravity-sdk';
const orchestrator = new AgentOrchestrator({
  model: 'gemini-3.5-flash',
  parallelAgents: 4,
  sandboxed: true,
});
const result = await orchestrator.run({
  intent: "Add async payment processing with OpenTelemetry tracing",
  subagents: [
    { role: 'refactor',      focus: 'async patterns' },
    { role: 'observability', focus: 'tracing instrumentation' },
    { role: 'testing',       focus: 'integration test suite' },
    { role: 'review',        focus: 'cross-agent consistency' }
  ]
});