Three Boundaries I Draw Before Handing Work to an Antigravity 2.0 Agent
What to hand a background agent, and what to keep in your own hands. The three boundaries I actually drew while running solo-dev automation in parallel, and how to encode them so the lines hold.
When the Antigravity CLI Stalls on a 401 During Unattended Runs
If your scheduled Antigravity CLI job suddenly stops producing output after a single 401 in the logs, here is how to separate an expired token from a silent re-login prompt and rebuild your unattended setup.
Ask Antigravity CLI Once Whether It Actually Answers, Right Before a Scheduled Run
When Gemini CLI shuts down on June 18 and you move to Antigravity CLI, an expired token or a bad first day can let an unattended job fail silently. Here is a preflight that probes the CLI once, classifies the failure, and decides whether the real job should start at all.
Measuring the Go-Based Antigravity CLI's Responsiveness to Rethink My Nightly Batch
The Antigravity CLI was reimplemented in Go, and startup and first-response feel different now. I measure startup, time-to-first-token, and throughput as three separate intervals, then use those numbers to move my nightly batch from serial to parallel.
Generating Multilingual Release Notes with the Managed Antigravity Agent via the Gemini API
A hands-on record of building a pipeline that turns git commit logs into multilingual App Store and Google Play release notes using the Managed Antigravity Agent, now in public preview through the Gemini API.
Putting a Verification Step After 'Done': Confirming What Your Antigravity Background Agents Actually Produced
An Antigravity 2.0 background agent reported 'Done,' yet the output was nowhere to be found. Running several sites on autopilot as a solo developer, I hit this gap more than once. Here is how I learned to check ground truth instead of the agent's self-report.
Does the New CLI Do the Same Job? An Output-Parity Gate Before Switching to Antigravity CLI
With Gemini CLI shutting down on June 18, here is how I froze the old CLI's artifacts as a golden baseline and built a parity harness to catch regressions before cutting over to Antigravity CLI — with normalization and a go/no-go gate, in code.
Running Multiple Repositories in Parallel with Antigravity 2.0 Projects and Worktrees
Combining Antigravity 2.0 projects with git worktrees to run several repositories in parallel safely. From isolating agent workspaces to avoiding conflicts and connecting to scheduled execution, organized from real work.
Before Gemini CLI Shuts Down (June 18): Audit Every Hidden Dependency Before Moving to Antigravity CLI
When Gemini CLI shuts down on June 18, the things that actually break are not in your terminal—they're the gemini calls buried in CI, git hooks, and cron. Here's how to surface every reference, validate with a dry run, and design a rollback before you cut over.
Calling a Managed Antigravity Agent from the Gemini API: Design Notes on the Preview Model
antigravity-preview-05-2026, now in public preview on the Gemini API, is a Managed Agent that plans, runs code, edits files, and browses the web autonomously inside a sandbox. Here is how it differs from rolling your own orchestration, and where to draw the line.
From Gemini CLI to Antigravity CLI: A Working Record of the June 18 Migration
On June 18, Gemini CLI and the Code Assist extension stop serving individual users. Here is my actual record of moving to the Go-based Antigravity CLI: what broke, the command mapping, and the auth and quota traps I hit.
Turning 'the Antigravity CLI feels faster' into a number with hyperfine
The Go-based Antigravity CLI feels snappier to start. Here is how to turn that impression into a reproducible number with hyperfine: warm vs cold runs, cumulative cost in automation, and a CI gate that catches regressions.