One Argument Now Switches Your Model in Antigravity CLI — and Rewrites Your Default Too
In CLI v1.1.22, /model takes an argument, switches instantly, and saves that model as your default in the same stroke. Here is the forget-to-switch-back trap that comes with it, and the start-of-session habit that fixed it for me.
Three things I had to fix before my status line could tell me what a session cost
Getting real session cost into a custom Antigravity CLI status line took three fixes: how the script reads stdin, how to tell whether your build sends a cost field, and how to keep a usage ledger that does not double-count.
Redrawing Your Workspace Boundary Now That Review Mode Auto-Approves Reads
Antigravity CLI 1.1.20 made in-workspace reads auto-approved in review mode. Here is what I found when I actually counted what became readable across two real working trees.
The pipe in my wrapper was swallowing Antigravity CLI's exit code
CLI 1.1.14 surfaces language server failures as a non-zero exit. That improvement never reaches you if your automation wrapper drops the exit code first. I ran sixteen calling patterns on bash 5.1 and recorded which ones make the failure disappear, plus the fixes that bring it back.
Why I Check Description Overlap Before Turning On inheritCustomizations
CLI 1.1.14 collapsed markdown agent inheritance into a single inheritCustomizations switch. Here is what happened when I actually inventoried the 47 skills in my workspace and decided the switch on description overlap rather than on context size.
When an Unattended Run Finds Its Working Folder Owned by Someone Else
A schedule that had been green for weeks failed one morning because it could not write .git/config. The cause was ownership drift on a reused working folder. Here is how to tell apart the read-but-not-write trap, probe writability for real, and fall back to a folder you can always write.
The Day the Article I Asked It to Format Became the Agent's Instructions
When you run an unattended content-formatting pipeline with Antigravity CLI, instruction-like text buried in the file you are processing can hijack the agent. Here is how I separate the instruction channel from the data channel and add an output-scope acceptance gate to reject anything out of bounds.
From Gemini CLI to Antigravity CLI: Migrating Without Stopping Your Automation
Gemini CLI has been retired and the Go-rewritten Antigravity CLI is now its successor. If you have the CLI wired into CI or scheduled jobs, swapping everything at once will break your automation. Here is a concrete plan for migrating gradually, from parallel testing to full cutover.
On Cutover Day to the Antigravity CLI, Verify Production Automation by Side-Effect Equivalence, Not Output
On the day you switch from the Gemini CLI to the Antigravity CLI, verify production automation by the equivalence of side effects — files written, commits, network calls — instead of matching stdout. A sandbox parallel run and a go/no-go cutover gate, with implementation steps.
When Your Agent Got 4x Faster: Rebuilding the Parallel Pipeline
When the Antigravity CLI moves to a faster model, the bottleneck in your parallel agent pipeline shifts. Here is a practical way to rethink verification, task granularity, concurrency, and cost caps with speed as the new baseline.
From Gemini CLI to Antigravity CLI: A Working Record of the June 18 Migration
On June 18, Gemini CLI and the Code Assist extension stop serving individual users. Here is my actual record of moving to the Go-based Antigravity CLI: what broke, the command mapping, and the auth and quota traps I hit.
Turning 'the Antigravity CLI feels faster' into a number with hyperfine
The Go-based Antigravity CLI feels snappier to start. Here is how to turn that impression into a reproducible number with hyperfine: warm vs cold runs, cumulative cost in automation, and a CI gate that catches regressions.