Delegate the Undoable, Guard the Irreversible — Tiering Agent Autonomy by Reversibility
When you hand production work to an Antigravity agent, the thing that bites first isn't intelligence — it's whether the operation can be undone. Here is a design that sorts every operation into three reversibility tiers and routes each to auto-execution, checkpointed execution, or a human gate, with TypeScript implementations and real numbers from running six apps in parallel.
Keeping Secrets Out of Your Antigravity Agent's Output: Layered Defenses for Logs, Diffs, and PR Bodies
The three paths through which background agents leak secrets, and how to defend commit diffs, execution logs, and PR bodies with layered protection, drawn from running six apps and measured false-positive rates.
Fixing self-signed certificate in chain When Antigravity Can't Connect
On networks with a corporate proxy or antivirus TLS inspection, Antigravity may log self-signed certificate in chain or unable to verify the first certificate and fail to reach the model. Here is what causes it and how to fix it.
Teaching Antigravity's Agent to Keep Diffs Small: How a Month Changed the Way I Review
When an agent hands you one giant diff, a solo developer's review can't keep up. After a month of asking Antigravity to break work into small steps first, here's how the experience of reviewing changed — with the exact instructions I now use.
Rehearsing an Agent's Actions Before They Touch Production — Designing a Zero-Side-Effect Dry-Run Layer
Some accidents survive shadow mode and canaries: the very first time an agent touches an external API. This is the design and TypeScript implementation of a zero-side-effect dry-run layer you can bolt onto Antigravity's parallel agents, with the real numbers from running six sites autonomously.
Capping Parallel Agents With a Token Budget — Designing a Guard That Stops Runaway Cost
Running many agents in parallel quietly inflates your token bill. This is not about shrinking prompts — it is about a governance layer that meters spend in real time and cuts it off at a budget. Full design and TypeScript implementation, drawn from running six sites autonomously.
Fixing spawn npx ENOENT When an Antigravity MCP Server Won't Start
Your MCP server config JSON looks correct, but Antigravity logs spawn npx ENOENT and the server stays gray. This is almost always a PATH inheritance problem, not a broken server. Here is how to diagnose and fix it.
Migrating Wallpaper Apps to Mandatory Edge-to-Edge on targetSdk 36 with Antigravity
The moment I bumped targetSdk to 36 (Android 16), the toolbar in my wallpaper preview screen slid under the status bar clock. Here is a working memo on handling the now-unavoidable edge-to-edge enforcement across several apps with Antigravity's agent.
Rolling Back a Half-Finished Agent: Compensating Transactions for Partial Failure
When you let an Antigravity agent run work that spans several external systems, a failure in the middle leaves the world half-rewritten. Retrying doesn't fix that. Here is how to fold it back safely with compensating transactions (the Saga pattern), with TypeScript and real operational numbers.
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.
Flow Control for Autonomous Agents: Backpressure and Queues That Keep Production Alive
Run several Antigravity agents at once and the problem stops being how smart they are and becomes how little your downstream can absorb. Here is a flow-control design — bounded queue, semaphore, token bucket, backpressure, dead-letter — with TypeScript and real numbers.