ANTIGRAVITY LABJP
TAG

Agent Operations

17 articles
Back to all tags
Related:
Antigravity10Antigravity CLI2Git2AGENTS.md2Antigravity 2.02Claude Code1permission design1unattended runs1WordPress1Host Migration1DNS1Verification1
Agents/2026-06-28Intermediate

Prune an Antigravity plan before you approve it

Instead of approving a Planning-mode plan wholesale, cut the one risky step and keep the rest. A field-tested look at partial plan editing from a solo developer's desk.

Editor/2026-06-22Intermediate

Precedence for Nested AGENTS.md: A Merge Design for Many Projects in One Workspace

Put several projects in one workspace, each with its own AGENTS.md, and which instruction the agent follows turns ambiguous. Root and per-project rules quietly collide; one wins, or both blend. Taking 'closer is stronger' as the base rule, this designs a merge that distinguishes overriding from appending, with working Python and field notes.

Tips/2026-06-12Beginner

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.

Agents/2026-05-20Advanced

Prompt Caching and Context Strategy for Antigravity Agents — Cutting 60-80% Off Monthly API Costs in Long-Running Production

The longer you keep agents running, the more the monthly invoice quietly piles up. Running Antigravity agents alongside an AdMob-monetized indie app business (50M cumulative downloads), I managed to cut API costs by 60-80% by rebuilding prompt caching and context strategy. This article shares the three-layer cache, context compression, and TTL design I now run in production — with the code and numbers behind them.

Agents/2026-04-28Advanced

Before Your Antigravity Agent Bill Goes Sideways: A Solo Developer's Forecast and Cutback Playbook

Discovering your monthly bill is an order of magnitude larger than expected is the first big trap of running agents. Here's the forecasting and cutback playbook I've built up as an indie developer, with concrete numbers, a working guardrail script, and the monthly review cycle I use.