All Articles
Keeping Scheduled Runs Reproducible: Pinning the Antigravity CLI Version to Tame Behavior Drift
The Go-based Antigravity CLI is now available to everyone, and updates are landing at a quick pace. When a CLI baked into your automation upgrades underneath you, a single morning's job can behave differently. Here is how I keep things reproducible — pinning the binary, recording its identity in each run's log, and rolling upgrades forward one job at a time — drawn from running four sites on an overnight schedule.
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.
Designing Safe Background Tasks with the Managed Agents API
Antigravity 2.0's Managed Agents API launches an agent in an isolated Linux environment with a single API call, handling reasoning, tool use, and code execution. Convenient, but left unattended it invites runaways and cost overruns. Here is a design for running it safely as a background task.
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.
When CLI, Desktop, and SDK Share One Agent Harness: Designing for Consistent Behavior
Now that Antigravity's CLI, desktop, and SDK share one agent harness, here is how to separate what stays consistent from what differs by environment, and how to align behavior with smoke tests and a version-tracking habit.
Your Antigravity Sandbox Isolates Multi-Agents Less Than You Think — Notes on Containing the Blast Radius
An Antigravity sandbox gives you the feeling of isolation, but isolation leaks through three real gaps: shared volumes, over-broad allowed domains, and approval fatigue. Field notes on plugging the leaks, containing the blast radius by design, and proving isolation holds with tests.
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.
From Gemini CLI to Antigravity CLI: Migrating Without Stopping Your Automation
Gemini CLI has been retired and the Go-rewritten Antigravity CLI is now its successor. If you have the CLI wired into CI or scheduled jobs, swapping everything at once will break your automation. Here is a concrete plan for migrating gradually, from parallel testing to full cutover.
Migrating to Antigravity 2.0 Without Stopping Your Automation: Parallel-Run and Rollback Design
How to move to Antigravity 2.0 without breaking running automation: how to set up a parallel-run window, verify output parity, pin versions, and keep a one-command rollback path, based on migrating four sites one at a time.
I Started the Ad SDK Before Asking for ATT — the Init-Order Bug That Quietly Lowered First-Session eCPM
When I rolled AdMob mediation out to four iOS apps, only the very first session showed weaker ad revenue. The cause was the order between the ATT prompt and MobileAds initialization. Here is why the order matters, plus how I had Antigravity audit the init sequence across all four apps.
Running Antigravity CLI Unattended: Notify Only on Real Failures
A small wrapper for scheduled Antigravity CLI runs that stays silent on success and alerts you only on failures a human needs to act on, covering exit codes, transient-error triage, and duplicate suppression.