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.
Android 17's Local Network Permission: Inventory Every LAN Call Site Before You Hand the Fix to an Agent
Apps targeting the new API level need explicit permission to reach the local network. A grep for private IPs found 2 of my 11 LAN paths. Here is the detector that found all 11, and how I turned its output into eleven checkable tasks for an agent.
Moving Antigravity to a New Machine: What Carries Over, What You Rebuild, and What Belongs in the Repo
Settings Sync restores your theme and keybindings in minutes, but auth tokens, workspace indexes, and local LLMs do not follow. A practical three-layer model for migrating Antigravity to a new machine without losing a day.
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.
Migrating to Antigravity 2.0 Without Stopping Your Automation: Parallel-Run and Rollback Design
How to move to Antigravity 2.0 without breaking running automation: how to set up a parallel-run window, verify output parity, pin versions, and keep a one-command rollback path, based on migrating four sites one at a time.
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.
Does the New CLI Do the Same Job? An Output-Parity Gate Before Switching to Antigravity CLI
With Gemini CLI shutting down on June 18, here is how I froze the old CLI's artifacts as a golden baseline and built a parity harness to catch regressions before cutting over to Antigravity CLI — with normalization and a go/no-go gate, in code.
Before Gemini CLI Shuts Down (June 18): Audit Every Hidden Dependency Before Moving to Antigravity CLI
When Gemini CLI shuts down on June 18, the things that actually break are not in your terminal—they're the gemini calls buried in CI, git hooks, and cron. Here's how to surface every reference, validate with a dry run, and design a rollback before you cut over.
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.
A Compatibility Shim That Bridges Old Scripts to agy Before Gemini CLI Shuts Down
Ahead of the June 18 Gemini CLI shutdown, instead of rewriting every gemini call scattered across cron and CI at once, a thin compatibility shim can bridge them to the Antigravity CLI (agy). Here is the approach with working shell scripts.
Six Days Until Gemini CLI Shuts Down — Auditing Automation Dependencies and Migrating to Antigravity CLI
With Gemini CLI ending on June 18, here is a practical walkthrough for finding gemini command dependencies hiding in cron, CI, and shell scripts, then migrating and verifying them on Antigravity CLI.
Moving to the Antigravity CLI (agy): Shifting Your Scripts Off Gemini CLI Before the June 18 Shutdown — Without Downtime
A grounded walkthrough of Google's Antigravity CLI (agy): fastest setup, a no-downtime migration off Gemini CLI, a compatibility shim, the Pro vs Ultra cost break-even, and running recurring work with scheduled messages — based on actually moving my own repos across.