All Articles
Confirm Your Unattended Runs Survived a Point Release in 30 Seconds
As Antigravity ships point releases at a fast clip, how do you stop scheduled runs from quietly breaking after an update? Here is a lightweight smoke test that detects regressions against a golden output and rolls back automatically when it diverges.
Hearing the Audio an Agent Made, Right Inside the Conversation
A recent Antigravity point release added inline audio rendering in the conversation view. Here is how playing agent-made audio in place changes the way I audition sound assets for my apps.
Before Desktop and CLI Drift Apart: Put Agent Steps in One Versioned File
As Antigravity 2.0 multiplies entry points across desktop, CLI, and SDK, the instructions for the same task slowly diverge per surface. As an indie developer running several sites on autopilot, I lay out a design that consolidates the steps into a single versioned file each surface merely reads.
Strip Secrets Out of the Agent Logs You Keep: Designing a Redaction Layer
Once you start keeping logs from unattended agents, a token or API key eventually lands in them in plaintext. Rotating the key doesn't unmake the leaked log. This designs a redaction layer that reliably drops secrets right before the write, going beyond regex to register known secrets and mask them for certain, with working Python and field notes.
Tracing What a Long Agent Run Actually Did: Review That Starts From In-Conversation Search
How to use the in-conversation search added in Antigravity v2.1.4 as the starting point for reviewing long agent runs. Choosing search terms, the decision points to inspect, and reconciling with background-agent logs, with concrete steps.
Keeping Scheduled Runs Reproducible: Pinning the Antigravity CLI Version to Tame Behavior Drift
The Go-based Antigravity CLI is now available to everyone, and updates are landing at a quick pace. When a CLI baked into your automation upgrades underneath you, a single morning's job can behave differently. Here is how I keep things reproducible — pinning the binary, recording its identity in each run's log, and rolling upgrades forward one job at a time — drawn from running four sites on an overnight schedule.
Three Prompts I Tried When Antigravity's Code Felt Correct But Not Mine
When Antigravity's output runs but never quite fits your codebase, the gap is usually missing design context. Three prompting patterns for handing over intent — plus the cases where even that wasn't enough, from real indie development.
Measuring the Go-Based Antigravity CLI's Responsiveness to Rethink My Nightly Batch
The Antigravity CLI was reimplemented in Go, and startup and first-response feel different now. I measure startup, time-to-first-token, and throughput as three separate intervals, then use those numbers to move my nightly batch from serial to parallel.
Turning 'the Antigravity CLI feels faster' into a number with hyperfine
The Go-based Antigravity CLI feels snappier to start. Here is how to turn that impression into a reproducible number with hyperfine: warm vs cold runs, cumulative cost in automation, and a CI gate that catches regressions.
Keep Side Questions Out of Your Main Thread with Antigravity's /btw
How Antigravity 2.1.4's /btw slash command routes side questions to a disposable subagent so your main agent's context stays clean through long tasks.
A Week of Coding Hands-Free with Antigravity 2.0's Live Voice Transcription
Antigravity 2.0 added Gemini Audio-based live transcription right inside the editor. After a week of using it in real work, here's an honest take on how it differs from external dictation tools, how it handles technical terms, and where it actually earns its place.
This Week at Antigravity Lab: Five Posts on Deciding How Much to Hand Over to Agents
Editor's notes on five posts: sizing agent tasks by what you can review, delegating dependency updates by risk tier, a StoreKit 2 migration case study, and a Japanese UI setup guide.