ANTIGRAVITY LABJP
TAG

scheduled runs

4 articles
Back to all tags
Related:
Antigravity2automation2config.json1configuration1resilience1unified permissions1unattended operation1permission design1Antigravity CLI1abstraction design1Google Cloud1Antigravity 2.01
Integrations/2026-07-19Advanced

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.

Integrations/2026-07-11Advanced

Nobody Is There to Say Yes: Writing Unified Permissions as an Unattended Contract

The v2.2.1 unified permission system assumes a person is watching. On a 3 a.m. scheduled run, that assumption quietly breaks. Here is how I declared the policy up front as an allow / deny / queue contract so an unattended agent never stalls on a prompt no one can answer.

Integrations/2026-07-01Advanced

Distribution-Path-Agnostic Antigravity CLI Automation: Betting on Both the Consumer and Google Cloud Editions

The 7/1 announcement began offering the Antigravity CLI via the Gemini Enterprise Agent Platform too. Here is a design that abstracts your personal automation to run on either the consumer or Cloud edition, laid out with a wrapper and capability-detection scripts.

Antigravity/2026-06-23Advanced

When the Default Model Changes Underneath You: Pinning and Diff-Gating Scheduled Runs

Antigravity 2.0 promoted Gemini 3.5 Flash to the default fast model. It is a welcome upgrade, but any scheduled run that leaned on the default starts producing subtly different output one morning. Here is how I pin the model explicitly, fingerprint the output, and gate drift, sized for a solo developer's pipeline.