Related:
◈ Agents/2026-06-29Advanced
Spotting Agents That Are Alive but Stuck — Designing a Progress Heartbeat and Watchdog
The process is alive but the work isn't moving — the nastiest state for a background agent. Here is how to switch from liveness to progress monitoring to detect it, and how to stop it safely, with working code.
◈ Agents/2026-06-29Advanced
When Background Agents Run Twice — Stopping Double Execution with Leases and Fencing Tokens
The same scheduled job fires from two machines at once and they overwrite each other's output. Here is how to stop that failure mode at the root in Antigravity 2.0 background agents, using leases and fencing tokens, with working code.
◉ Antigravity/2026-06-16Intermediate
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.