All Articles
Four Reasons Your .antigravityignore Rules Are Not Taking Effect
Rules that quietly do nothing, and rules that swallow the whole repository. Here are four causes behind both, each checked one at a time against a gitignore-style matcher.
The pipe in my wrapper was swallowing Antigravity CLI's exit code
CLI 1.1.14 surfaces language server failures as a non-zero exit. That improvement never reaches you if your automation wrapper drops the exit code first. I ran sixteen calling patterns on bash 5.1 and recorded which ones make the failure disappear, plus the fixes that bring it back.
When Antigravity Holds a Dozen Projects: How I Stopped Hunting for Yesterday's Conversation
As Antigravity projects pile up, the conversation sidebar turns into a morning scrolling ritual. Now that 2.8.0 remembers collapsed state, here is how I reworked project granularity, conversation naming, and launch flags.
Seven Characters Don't Only Point at Commits — Measuring When Your Agent's Recorded Hashes Stop Resolving
Short commit hashes recorded by an agent quietly stop resolving as a repository grows. Measuring where ambiguity begins, fixing the recording side, and building a batch verification gate.
When the JSDoc an AI Wrote Quietly Stopped Matching the Code: Field Notes on Measuring Documentation Drift
AI-generated JSDoc gets written once, looks authoritative, and is then trusted and left to rot. Field notes on hashing function signatures to detect staleness, tracking a drift rate, and fixing only the blocks that actually diverged.
Moving Antigravity to a New Machine: What Carries Over, What You Rebuild, and What Belongs in the Repo
Settings Sync restores your theme and keybindings in minutes, but auth tokens, workspace indexes, and local LLMs do not follow. A practical three-layer model for migrating Antigravity to a new machine without losing a day.
You Can Measure a Request Before You Send It — Sizing Agent Tasks by Working Backward from Rework Rate
When an Antigravity agent returns code that misses the mark, the cause is rarely the wording of the prompt. It is the size of the task. Here is a Python scorer that grades a request before you send it, plus what happened when I scored 80 past requests against their actual rework outcomes.
When Lighthouse Is Green but Search Console's Core Web Vitals Are Red — Field Notes on Naming the Slow Interaction with Real-User Data
Lighthouse scores in the 90s, yet field Core Web Vitals won't budge. Here is how I closed the lab-vs-field gap with real-user monitoring (RUM), named the exact interaction driving a slow INP, and fixed it with Antigravity.
When Antivirus Blocks Antigravity's Launch, Verify the Signature Before You Allow It
When the Antigravity desktop app won't launch because antivirus stepped in, here's how to tell a false positive from a real threat. Verify the code signature on macOS Gatekeeper and Windows Defender first, then allow-list with the narrowest possible scope.
When Your Agent's Commits Pick Up Junk Files: Fixing It With Staging Scope and a Message Convention
Agents tend to run git add -A, sweeping .bak files and caches into your history, and leave a one-word message. Here is how a staging allowlist, a preflight, and a fill-in message template stop it.
Where Context Should Live — Routing It Across Persistent, Per-Task, and In-the-Moment Layers
Antigravity 2.0's /btw lets you inject context mid-task. But unless you separate what belongs in a persistent rule, a task instruction, and a passing aside, your agent's accuracy actually drops. Here is a design for three context layers.
Don't Let Your Automation Lean on AI Ultra's 5x Ceiling
The $100/month AI Ultra plan raises Antigravity's usage limits to 5x AI Pro. But if you architect automation around that ceiling, it collapses the moment you drop back a tier. Here is a limit-independent degradation design, with the real pain points.