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.
Calling Local LLMs from Antigravity — Ollama and LM Studio Integration in Practice
Running local LLMs from Antigravity through Ollama or LM Studio — with a real benchmark harness, a monthly breakeven model, and a wrapper that forces JSON output. The evidence you need to decide, on both confidentiality and API cost.
Localizing Antigravity 2.0 to Japanese — The Three-Layer Setup for Menus, Commands, and AI Responses
Installing the Japanese Language Pack in Antigravity 2.0 only translates part of the UI. To get a clean Japanese experience — menus, command palette, AI responses — you need to configure three independent layers. Here is the exact setup I run as an indie developer at Dolice, plus which parts I deliberately leave in English.
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.
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.
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.
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.
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.
The Thumbnails Had Been Drifting: Catching Image-Asset Regressions with pHash and SSIM in Your Agent Workflow
After letting an agent rewrite an image pipeline, visual quality can quietly slip in ways tests never catch. This guide shows how to measure that drift with two numbers — pHash and SSIM — and block it in CI, from threshold calibration to a ready-to-run gate script and Antigravity integration.
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.
Before Your Finger Learns the Approval Dialog: Folding Antigravity Permissions Into One Policy
Scattered approval dialogs, per-MCP allowlists, repeated re-auth. Built around Antigravity 2.2.1's unified permissions and OAuth keyring storage, here is how I fold every permission into a single policy and design away approval fatigue, with working code and measured numbers.
When Parallel Agents Ran the Same Task Twice and Quietly Doubled the Bill — Field Notes on Measuring and Stopping Duplicates
The bill for our parallel agents came in about 1.9x higher than expected — because multiple workers were running the same task twice. These are field notes on measuring the duplication, stopping it with idempotency keys, and attributing cost per task.