Gating Your Agent's Commits With pre-commit — Keeping Broken Changes Out of the Main Repo
How to wire up a pre-commit gate that lints, type-checks, runs fast tests, and scans for secrets the moment Antigravity's agent commits — with measured timings and the ordering that keeps it fast.
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.
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.
When Your Agent Got 4x Faster: Rebuilding the Parallel Pipeline
When the Antigravity CLI moves to a faster model, the bottleneck in your parallel agent pipeline shifts. Here is a practical way to rethink verification, task granularity, concurrency, and cost caps with speed as the new baseline.
Making My Managed Agents Batch Survive a Crash Without Redoing Everything
Running a 200-item batch on the Managed Agents API kept torching tokens, because every mid-run failure restarted from item one. Here is the checkpoint-and-idempotency design I added so the batch resumes from where it died.
Before You Trust 'It's Fixed' — Make the Agent Confirm Your Live URL Actually Renders
The agent reported it had fixed the bug and deployed successfully, yet the production page was blank. To prevent the empty-body-with-200 trap, here is how to add a completion gate that makes Antigravity 2.0's Browser Sub-Agent open the live URL and confirm the main content selector is actually filled.
Stopping an AI Agent from Skipping Quality Checks — A Two-Layer Push Gate with Antigravity CLI Hooks and git pre-push
An agent once judged my failing tests 'unrelated' and pushed anyway. Here is the two-layer gate — Antigravity CLI hooks plus git pre-push — I now rely on.
When a Scheduled Agent Runs Twice — Designing for Idempotency Against Overlap and Retry
A scheduled agent can do the same work twice when the next run triggers before the last one finishes. Here is a design with an overlap lock and an idempotency guard that survives mid-run failures, drawn from a double-publish incident I ran into in production.
Instruction Drift in Scheduled Agents — A Three-Layer Design for Keeping Definitions, Docs, and Reality Aligned
Scheduled agents keep logging success even after their instructions diverge from reality. Here is the three-layer drift-detection design — definition, documentation, reality — I built after silent failures in my own operations.
Running Multiple Agents on One Repo Breaks It — Isolating Work Areas with Worktrees
When you run several Antigravity 2.0 agents against the same repository, you hit index.lock collisions and half-staged commits. Here is an isolation design using git worktree and projects that gives each agent its own work area, drawn from an incident I ran into in production.
Building Idempotent Scheduled Agents with the Antigravity SDK
Scheduling an Antigravity SDK agent is almost a one-liner. The hard part is making it idempotent — so a double trigger never runs the job twice, a crash never drops a day, and the result always converges to one. Here is how I build idempotent scheduled agents, learned from the maintenance jobs I run as an indie developer.
Handing Dependency Updates to Antigravity Agents — Risk Tiers, Verification, and Rollback
How far can you trust Antigravity agents with dependency updates? A four-tier risk model that corrects semver optimism, worktree-isolated lots, a fixed verification script, and a rollback-first ledger — the operations design I settled on while maintaining multiple apps.