All Articles
Containing Failure in Antigravity Multi-Agent Systems: Three Boundaries That Stop Cascades
Antigravity multi-agent setups run beautifully in isolation but cascade in production, where one small failure drags the whole orchestration down. These notes organize the fix around three boundaries—layered control, trust separation, and observability with idempotency—down to the TOML and the correlation-ID wrapper.
Designing Schema Evolution So Sub-Agent Handoffs Never Break
Put a typed contract at the boundary where a downstream agent receives an upstream agent's output, and learn how to evolve that schema without breaking existing flows — with validation code, a migration sequence, and the production symptoms to watch for.
When Managed Agents Run in the Cloud, How Do You Hand Them Credentials?
The Antigravity 2.0 Managed Agents API runs agents in the cloud, away from your machine. Convenient, but the credential handling that was trivial on your own laptop suddenly gets hard. Here is a design for not handing over long-lived tokens, but issuing them per run and expiring them quickly.
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.
Designing Parallel Agent Changes So You Can Trace Them Later
Antigravity 2.0 became a control tower for many agents. Here is how to build an audit trail that lets you trace who changed what and why, designed from real operational failures.
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.
When an AI Agent's git push Reports Success but Nothing Reaches the Remote
Why agent-automated git pushes fail silently (a missing identity plus a no-op push), with three fixes: explicit config, SHA verification, and the GitHub REST API.