Antigravity 2.0, CLI, IDE, or SDK — How to Pick the Right Surface
Antigravity ships as a desktop app, a CLI, an IDE, and a Python SDK. This guide cuts through the four surfaces and gives you a simple decision path for picking the right entry point for the work in front of you.
Your Antigravity Custom Tools Don't Break by Design — They Break on Re-execution: Field Notes on Idempotency and Error Contracts
Once you add a custom tool to an Antigravity agent, the real production problem is re-execution and duplicated side effects. Here are the idempotency keys, error contracts, health gates, and tool-sprawl checks that actually held up in practice.
Tracing What a Long Agent Run Actually Did: Review That Starts From In-Conversation Search
How to use the in-conversation search added in Antigravity v2.1.4 as the starting point for reviewing long agent runs. Choosing search terms, the decision points to inspect, and reconciling with background-agent logs, with concrete steps.
Keeping Unattended Agent Run Logs Long Enough to Debug — Without Filling the Disk
A scheduled agent is only fixable if you can reconstruct why it failed. Here is how to keep run logs around without filling the disk — tiered retention, schema-versioned records, and a compaction job — drawn from running four sites on autopilot as an indie developer.
Agent Config Drifts Quietly Across Environments: Detection and Correction
Across two Macs and an automation host, agent settings slowly diverge and only one side fails. Here is how to surface that config drift with normalized hashing and a correction workflow, from an indie developer's setup.
A Schedule That Survives 429s: Backoff and Jitter for Agent Automation
Run agents in parallel and rate-limit 429s can cascade until everything dies. Here is how to design exponential backoff and jitter so the retries themselves don't create new congestion, from an indie developer's automation setup.
When a Timed-Out Unattended Agent Leaves a Half-Written File Behind
When a scheduled agent gets killed on timeout, it can leave a half-written file that silently poisons the next stage. Here is the atomic write, stale-temp cleanup, and post-write content assertion I use to keep unattended pipelines from breaking.
Don't Lose Failed Agent Jobs: Designing a Dead-Letter and Requeue Path
Scheduled agents fail silently overnight and the work simply vanishes. Here is how to catch those failures with a dead-letter store and a staged requeue, drawn from running four sites on autopilot as an indie developer.
More Agents Won't Speed Up Every Part of Your Pipeline — Designing the Parallel/Serial Line
Antigravity 2.0's parallel multi-agent execution is powerful, but adding agents doesn't make everything faster. Here's how I decide which work to parallelize and which to keep serial, derived from invariants and a dependency graph, with examples from running several sites as a solo developer.
How to Orchestrate Multiple Agents: Drawing the Line Between Parallel and Serial Work
Antigravity 2.0 brings true parallel execution across multiple agents. But making everything parallel does not make it faster. Which work should fan out in parallel, and which should stay serial? This is an orchestration design that does not fall apart, viewed through dependencies and contention.
Parallel or Keep It Serial: The Break-Even Point When Orchestrating Multiple Agents
Should you run agents in parallel or keep them serial? A simple way to estimate the break-even between coordination cost and saved wall-clock time, plus how I actually split parallel vs serial across four scheduled sites.
Handing Visual Regression to a Parallel Agent in Antigravity 2.0
A design for running a dedicated headless visual-regression agent alongside your main implementation agent using Antigravity 2.0's parallel orchestration — with a working harness and the reproducibility traps I hit in production.