What @ Includes Actually Shrink When You Split Agent Rule Files
I split my rule files using Antigravity 2.11.0's @path/to/file includes and measured the before and after across four real repositories. Maintenance surface dropped 62 percent. What a session actually reads dropped 1.7 percent. Here is why, plus the code that catches the silent failure mode.
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.
Adding MCP Servers Without Opening the Config File: The agy mcp Subcommand
Antigravity CLI 1.1.16, released on August 20, adds an mcp subcommand so you can register and toggle MCP servers without hand-editing JSON. Here is how to add stdio and HTTP servers, isolate a misbehaving one, and script your whole setup so it travels to a new machine.
Find the one broken MCP entry before Antigravity starts, with 40 lines of Node
A single typo in your MCP settings can take every server down with it. Here is a small preflight script that catches the mistakes statically, the real output from a deliberately broken config, and the duplicate-key trap that JSON hides from you.
A Typo in agent.md Quietly Widened My Permissions — Writing a Strict Frontmatter Lint
Misspelled keys in agent.md frontmatter do not raise errors. They fall back to defaults, and for permission fields that fallback points the wrong way. Here is the failure I hit, the lint I wrote to catch it, and what the measurements showed.
The One File That Stops Startup: Guarding config.json Integrity Before Scheduled Runs
Antigravity 2.3.1 fixed a bug where an empty or corrupt config.json blocked startup. The symptom was fixed; the causes of corruption still live in your environment. Here is a three-layer guard — validate, snapshot, restore — that runs before a scheduled job, with working code and notes from running it nightly.
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 Your MCP Servers Vanish From the Chat App in Antigravity 2.0
After Antigravity 2.0 split into an IDE and a separate chat-style agent app, an MCP server I had set up in the IDE stopped showing up on the chat side. Here is why the settings scopes are separate, and how to fix it by making a single workspace-level source of truth that both apps read.
Agent Config Drifts Quietly Across Environments: Detection and Correction
Across two Macs and an automation host, agent settings slowly diverge and only one side fails. Here is how to surface that config drift with normalized hashing and a correction workflow, from an indie developer's setup.
When Antigravity Ignores Your AGENTS.md — How to Diagnose and Fix It
You dropped an AGENTS.md at the repo root with clear rules, but the agent still pulls in banned libraries and blows past your conventions. Here is how I diagnose and fix the three most common causes I have seen across more than a hundred Antigravity sessions.
Antigravity Settings Sync Not Working Across Devices: A Layered Troubleshooting Guide
When Antigravity Settings Sync fails between machines, the cause is almost always one of four layers: auth, local cache, network, or scope. Here are the diagnostic steps that actually work.
Antigravity Local LLM Not Connecting: Four Causes to Check First
Can't get Antigravity to connect to your local LLM? This guide covers all four failure patterns — Ollama not running, LM Studio server not started, VRAM issues, and macOS firewall blocking — with diagnostic commands and step-by-step fixes.