All Articles
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.
As Tools Consolidate Into Antigravity, Measure Your Lock-In and Keep an Exit Path
As Google consolidates its AI coding tools into Antigravity and the personal Gemini CLI sunsets on June 18, here is a practical design for quantifying vendor lock-in and keeping a configuration you can step away from at any time.
After Gemini 3.5 Flash Became the Default, Route Flash and Pro Per Task
Now that Antigravity's default Flash is Gemini 3.5 Flash, leaving everything on Flash wastes accuracy and forcing everything onto Pro wastes time. Here is a two-axis decision table for splitting work between Flash and Pro, plus the routing setup to wire it into your agents.
A Compatibility Shim That Bridges Old Scripts to agy Before Gemini CLI Shuts Down
Ahead of the June 18 Gemini CLI shutdown, instead of rewriting every gemini call scattered across cron and CI at once, a thin compatibility shim can bridge them to the Antigravity CLI (agy). Here is the approach with working shell scripts.
Budgeting Quota So Parallel Agents in Antigravity 2.0 Don't Run Dry
Run several agents at once in Antigravity 2.0 and your quota can be gone by mid-afternoon, right when you need it for the real work. Here is how I measure per-agent consumption, find the Pro-vs-Ultra break-even, and budget so I never hit the ceiling.
Running Antigravity Behind a Proxy — Connection Design for Corporate Networks, SSL Inspection, and Hotel Wi-Fi
Keep Antigravity working behind corporate proxies, SSL inspection, and hotel Wi-Fi: layer-by-layer diagnosis, certificate trust, NO_PROXY design, and connection profiles with a local LLM fallback.
Six Days Until Gemini CLI Shuts Down — Auditing Automation Dependencies and Migrating to Antigravity CLI
With Gemini CLI ending on June 18, here is a practical walkthrough for finding gemini command dependencies hiding in cron, CI, and shell scripts, then migrating and verifying them on Antigravity CLI.
Measuring the Break-Even Point Between Google AI Pro and Ultra — 14 Days of Quota Data from Parallel Agent Runs
Is AI Ultra ($100/month, 5x the Pro limits) actually worth it? A Python harness that aggregates daily quota consumption from agent logs, 14 days of real measurements, and a formula that converts wait time into money to settle the question.
Why Antigravity Agent Edits Fail With 'patch does not apply' and How to Fix It
Why Antigravity agent edits stall with 'patch does not apply' or 'hunk failed', and how to fix it. Focused on the race where the file changes after the agent reads it, with the settings that stop it from recurring.
Two Months of Maintaining Four Wallpaper Apps with Antigravity and git worktree
A record of two months running Antigravity's agent alongside git worktree to maintain four wallpaper apps in parallel. How the branch-switching tax disappeared and the agent's work stopped bleeding together.
Keeping Agent Behavior Consistent Across Separate Repositories: Notes on Multi-Repo Governance
How to keep Antigravity agents behaving consistently across several independent repositories when a monorepo isn't an option. A layered governance design with a working distribution script and drift audit, drawn from running four sites in parallel.
Why Your Antigravity Agent Stops Mid-Task with 429 RESOURCE_EXHAUSTED, and How to Fix It
When you hand a long task to an Antigravity agent, it sometimes halts halfway with a red 429 RESOURCE_EXHAUSTED. That is a rate-limit or quota signal, not a bug. Here is how I diagnose the three flavors of 429 in production, and how to keep your agent from stalling on the same wall twice.