All Articles
Handing Crashlytics Stack Traces to Antigravity — Three Weeks Across Four Apps
Paste a Crashlytics stack trace into Antigravity, let it narrow the cause, and drive the fix to the finish. After three weeks across four wallpaper apps, here is what I learned to delegate and what I kept for myself.
Build for the Day the Agent Breaks Something: Keeping Blast Radius Small
Once you let an Antigravity agent touch production, the problem stops being how smart it is and becomes how much it wrecks when it slips. Here is a four-layer containment design that shrinks blast radius, with TypeScript and real numbers.
Designing a Negative Spec for Antigravity Agents — The Forbidden-Territory List I Use Across 50M-Download Apps
Hand your Antigravity agents a list of things they must never touch — not just what they should do. Here is the FORBIDDEN.md template, subagent bootstrap, and reinjection script I run across 6 indie apps and 50M downloads.
Copilot Studio's Computer-Using Agent Next to How I Run Claude in Chrome Every Morning
Microsoft made Copilot Studio's Computer-Using Agent generally available. Here is how that announcement looks from the perspective of an indie developer who already runs Claude in Chrome against AdMob and Crashlytics every morning.
Why Antigravity Agent Edits Vanish with Auto Save (and How to Stop It)
When Antigravity's agent stream collides with the editor's Auto Save, parts of an applied diff silently disappear. This guide walks through the exact conditions that trigger it and a three-step fix you can keep across projects.
A Month with Antigravity Inspector — Reading the Agent's Real Behavior
Notes from a month of seriously using Antigravity's Inspector while maintaining four wallpaper apps. The reading order I settled on, the panels I actually look at, and the pitfalls that quietly mislead you.
Supervising Long-Running Antigravity Agents — Watchdog and Tiered Recovery
Eight weeks of running AdMob revenue optimization on Antigravity background agents revealed three quiet failure modes. Here is the watchdog plus tiered recovery design I landed on.
What Qwen3.7-Max's '35-Hour Autonomous Run' Means in Practice — Design Notes from an Indie Dev Running Both Antigravity and Claude Code
Alibaba's Qwen team published a demo where Qwen3.7-Max ran autonomously for about 35 hours and made over 1,158 tool calls. I walk through what that number means for a one-person shop using both Antigravity and Claude Code, and how to translate the design lessons into a personal evaluation set.
Recovering Missing iOS dSYMs Across Six Apps with Antigravity's Background Agent — A Four-Week Operations Log
After migrating Firebase iOS SDK from CocoaPods to SPM, six wallpaper apps saw their Crashlytics symbolication rate collapse to as low as 4.2%. This is a four-week operations log of letting Antigravity's Background Agent track, upload, and verify 1,847 missing dSYMs across six repositories — including App Store Connect dSYM polling and AdMob revenue reconciliation.
Fixing Antigravity Google Sign-in That Won't Return From the Browser
When you press Sign in with Google in Antigravity and the browser just hangs without returning to the editor, the cause is rarely a single thing. Here is how I narrow it down across four layers — callback port, third-party cookies, stale session files, and network path — using only commands I keep close on every machine.
Forensic Audit Trail for Antigravity Background Agent — Cloudflare R2 logging that reconstructs decisions six months later
How to design a decision-log audit trail for long-running Antigravity Background Agents so you can still reconstruct why an agent did what it did six months later — schema, R2 write layer, PII masking, and Polars queries.
Five Weeks Letting Antigravity's Background Agent Refresh App Store Screenshots Across Four Apps
An operations log from running Antigravity Background Agent for five weeks to keep the App Store screenshots for four wallpaper apps in sync across eight locales — including the boundaries I kept, the recurring failure modes, and what I learned about where automation should stop.