◉ANTIGRAVITY LABJP
TAG

Agents

172 articles
← Back to all tags
Related:
antigravity91Antigravity55production25automation23troubleshooting14workflow12orchestration10operations8reliability8Python7architecture6multi-agent6
◈ Agents/2026-04-27Advanced

Letting Antigravity Be Your Night-Shift Engineer: A Solo Dev Operating Model

How to operate Antigravity agents as the second engineer who works while you sleep. Task hand-off, scope boundaries, and a morning three-point check turned into a script — the model I have refined while running multiple products solo.

◈ Agents/2026-04-26Advanced

Designing Antigravity Agent Traces That Tell You Why It Failed — Observability in Practice

How to add OpenTelemetry spans to your own agent loop so a failure can be read in a few lines. Covers span structure, what to keep and drop in attributes, a failure_class taxonomy, a retry table, three dashboard views, cost attributes, and PII handling — with code that runs.

◉ Antigravity/2026-04-25Advanced

Designing Antigravity Retry for Production — Idempotency, Backoff, Cost Ceilings, and Failure Triage

A production blueprint for Antigravity agent retry: idempotency, exponential backoff, token-budget ceilings, failure triage, and resumable checkpoints.

◈ Agents/2026-04-24Advanced

SRE for Antigravity Agents — Taming Probabilistic Systems with SLOs and Error Budgets

AI agents are probabilistic by nature, so running them in production without SRE thinking is risky. This guide applies SLIs, SLOs, and error budgets to Antigravity agents with working code, and shows why the textbook 14.4x burn-rate alert never fires on a loose SLO.

◈ Agents/2026-04-22Advanced

Prompt Injection Defense in Antigravity — A Production Security Playbook for LLM Apps

Build a four-layer prompt injection defense inside Antigravity with working Python. Includes measured heuristic recall across eight obfuscations and the normalization bug that breaks detection for non-Latin scripts.

◈ Agents/2026-04-22Advanced

Harness Engineering for Antigravity

A deep dive into 'harness engineering' for Antigravity — the prompt-and-template design that makes an agent complete a project, not just answer a question.

◈ Agents/2026-04-20Advanced

Building a Business Automation Agent with Antigravity × Google Workspace API — Gmail, Drive, Sheets and Docs in Production

Learn how to build AI agents that automate Gmail responses, generate documents from Drive templates, and create intelligent Sheets reports using Antigravity, Google Workspace APIs, and Gemini.

◈ Agents/2026-04-16Advanced

Building an AI Test Pipeline with Antigravity Agents: Automating Quality Assurance in Production

Learn how to build a production-grade automated test pipeline using Antigravity's AI agents — from unit test generation to E2E testing with Playwright, complete with validation layers and CI/CD integration.

◈ Agents/2026-04-01Advanced

Antigravity × A2A Protocol: Complete Implementation Guide for Scalable Multi-Agent Systems

A complete guide to implementing Google's A2A (Agent-to-Agent) protocol with Antigravity. From agent card design to task delegation, streaming communication, and production deployment on Cloudflare Workers.

▣ App Dev/2026-07-18Advanced

After Compose-First: Choosing Which View Screens to Migrate, Ranked by Churn Instead of Count

Google has declared Android development Compose-first. Here is how I rank View-based screens for migration using git history rather than screen counts, with the scoring script I actually ran and the three places partial migration quietly duplicates state.

◈ Agents/2026-07-17Advanced

Three Quarters of My Reference Notes Never Reached the Agent: Measuring What head Cuts Away

I fed reference notes to a scheduled agent with cat and head, and the lines that mattered were quietly cut. Here is the measurement, and how I replaced a line count with a section-level contract.

◈ Agents/2026-07-16Advanced

When to Hand Your Agent the Next Instruction: Waiting, Interrupting, and Queuing, Measured

Antigravity v2.3.0 added message queuing and Send Now. I measured waiting, interrupting, and queuing against the same yardstick, found that 41% of queued instructions arrive stale, and cut rework from 22% to 9% with a twenty-line stamp.