◉ANTIGRAVITY LABJP
TAG

antigravity

855 articles
← Back to all tags
Related:
agents123troubleshooting94automation68production59workflow49app-dev44ios35multi-agent34tips33editor31comparison26monetization26
✦ Tips/2026-07-10Advanced

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.

◈ Agents/2026-07-10Advanced

Tracing Why an Agent Wrote That Line Six Months Ago — Commit Granularity and Provenance Trailers

When an agent packs 14 files and 800 lines into a single commit, git blame tells you nothing six months later. Here is how I split commits at intent boundaries, recorded provenance as machine-readable Git trailers, and built a one-command path from a blamed line back to the design decision behind it.

◈ Agents/2026-07-10Advanced

When Your Agent's Files Vanish Into .gitignore — A Pre-Commit Detection Gate

When an agent writes files that match .gitignore, the diff review looks perfect but nothing lands in the commit. Here is a gate script that catches ignored build output before you push, plus the tuning it needs.

▣ App Dev/2026-07-09Advanced

Deciding When to Stop a Staged Rollout, Before You Have To — Agents Watch, I Halt

Field notes on building a Google Play staged-rollout watcher with Antigravity. Crash rate as a ratio to baseline, delayed ANR evaluation, and an explicit insufficient_data verdict — with the halt action kept in human hands.

▣ App Dev/2026-07-09Advanced

Background Refresh May Never Run — Measuring Execution Opportunity and Redesigning Around Freshness

Scheduling a BGTaskScheduler or WorkManager job is a request, not a guarantee. Here is how I instrumented execution opportunity, defined freshness as an SLO with p50 and p90 targets, and rebuilt the update path into three layers that hold up when background work never runs.

▣ App Dev/2026-07-09Advanced

Before an Agent's .proto Edit Silently Breaks Binary Compatibility: Gating Wire Compat with buf breaking

When an agent edits your .proto files, the text can look perfect while wire compatibility quietly breaks. Here is how to stop field-number reuse and unsafe type changes with a working gate built from buf breaking and reserved.

⟐ Editor/2026-07-09Advanced

Antigravity DevContainer: A Complete Setup Guide for Reproducible AI Development

An end-to-end guide to running Antigravity inside a DevContainer — Docker setup, Ollama integration, secrets, volume persistence, team distribution, and CI parity.

⟐ Editor/2026-07-08Intermediate

When Antigravity Reads Cloud-Synced Files as Empty: The Online-Only Placeholder Trap

A file is right there in Finder, yet the Antigravity agent insists it is empty or missing. The culprit is an online-only placeholder created by cloud sync. Here is how to spot it, hydrate the data, and design a workspace that avoids the problem.

◈ Agents/2026-07-08Advanced

Measuring the Rework Rate of What You Delegate to Agents: Drawing Delegation Boundaries with Numbers, Not Instinct

How much should you hand to an agent? I drew that line by instinct for a long time. Here is a practical way to compute a per-category rework rate from your git history and redraw the delegation boundary with numbers, with working code.

✦ Tips/2026-07-08Intermediate

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.

⬡ Integrations/2026-07-08Advanced

Antigravity Now Saves OAuth Tokens to the OS Keyring — Keeping Auth Alive in Headless Runs

In v2.2.1, refreshed OAuth tokens are saved to the OS keyring automatically. Pleasant on the desktop, but on headless scheduled runs the vault itself may not exist and auth quietly breaks. We design explicit backend selection, a safe file fallback, and per-location liveness checks.

⬡ Integrations/2026-07-08Advanced

When Successful Automation Quietly Stops Earning Its Keep: Designing for Value Decay and Retirement

A dashboard full of green success logs often hides the most dangerous kind of failure. Here is a design — with working code — for surfacing automations that keep succeeding while producing no value, and deciding whether to retire, repair, or keep them.