ANTIGRAVITY LABJP
TAG

agents

158 articles
Back to all tags
Related:
antigravity85Antigravity50production25automation23troubleshooting12orchestration10workflow9reliability8operations7architecture6multi-agent6Operations5
Agents/2026-07-13Intermediate

Passing API Keys to Agents Safely: Runtime Env Injection and Log Redaction

How to hand secrets to an Antigravity agent without leaving them in your repo or your logs, using runtime environment injection and output masking.

Agents/2026-07-12Advanced

What to Delegate to an Antigravity Agent and What to Keep by Hand, After Two Weeks

After two weeks of handing my daily solo-dev tasks to Antigravity agents, a clear line emerged between the work I was glad to delegate and the work I had to pull back. A retrospective with the operational log.

Agents/2026-07-12Advanced

The Scarier Permission Was Reach, Not Write: Locking an Agent's Outbound Traffic to an Allowlist

When I hand real work to an agent, the thing I guard most isn't file edits, it's where it connects. Here is an 80-line deny-by-default egress gate, plus what 21 nights of unattended runs revealed about the traffic I never saw.

Agents/2026-07-12Advanced

Clock Design for Agents: Separating Monotonic and Wall Time to Protect Long Runs

In scheduled and overnight agent runs, computing timeouts, retry backoff, and rate-limit windows from the wall clock breaks in quiet, hard-to-debug ways. This piece walks through a small Clock abstraction that splits monotonic from wall time, with a decision table and testable code.

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.

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.

Agents/2026-07-05Advanced

Protecting Your Agent Stack's Known-Good State with a Single Lockfile — Change-Budget Design for an Era of Simultaneously Moving Parts

When the IDE build, CLI, model, and dependencies all move at once, you can no longer tell which one caused a regression. Here is a change-budget design that pins your known-good state to one lockfile, with working code and operational logs.

Agents/2026-07-05Advanced

Make the Self-Debugging Agent Walk the Logged-In and Post-Paywall Screens

By default, Antigravity 2.0's real-browser self-debug only sees the logged-out free view and reports success. To catch billing regressions, inject an authenticated session and paid state into the agent's browser and force coverage with assertions.

App Dev/2026-07-02Intermediate

Stop Treating Dependency Updates as a Monthly Chore — Weekly Agent Runs with Semver Risk Triage and Verification Gates

Move from batch-updating 47 stale packages at once to a weekly agent-driven routine: semver-based risk tiers, a playbook YAML, hallucination-proof changelog reports, and a lockfile diff gate.

App Dev/2026-07-02Intermediate

Stop Dreading the Rejection Email: Triaging App Store Review Feedback with an Antigravity Agent

A working setup for feeding App Store rejection notices into Antigravity, classifying them against a guideline playbook, and gating resubmission with an Info.plist lint — with real turnaround numbers.