# Antigravity Auto reproduction

Run the same sequence on base 1d028248683f90f405b2d8e7b71682e3b67317ed and head 82c24d4ca20e134eece313e84d6b00d8dce6a5b2.

Environment: Linux web dev app, Chromium, 1280x800 CSS viewport, light theme; agy 1.5.14 with Gemini API key authentication. Fresh isolated state, T3CODE_DEV_SEED=0, GOOGLE_GEMINI_BASE_URL supplied in the server environment. No live database copied.

1. Start each checkout with `T3CODE_DEV_SEED=0 GOOGLE_GEMINI_BASE_URL="$GEMINI_BASE_URL" vp run dev`.
2. Create an empty git repository with one empty commit and add it as project **Auto mode demo** using the project CLI.
3. Add an Antigravity instance in Settings > Providers, use Gemini API key with a non-empty placeholder key. Set its binary path to the accompanying executable `agy` proxy. The real agy must be on PATH, or set AGY_REAL_BINARY.
4. Create an `advertise-auto` file beside the proxy, then connect or refresh the provider. The proxy adds auto to mode lists and config options while this file exists, exactly to reproduce the prior advertised-Auto state from triage. It forwards requests unchanged to real agy.
5. Start a new thread in Auto mode demo; choose Antigravity > Gemini 4 Hydrogen, Low thinking, Permissions: Auto. Collapse the sidebar and details panel on both sides.
6. Remove `advertise-auto`. All agy replies now pass through unchanged.
7. Record typing and submitting: **Run ls in this project and report the entries. Do not modify files.**
8. Inspect the real app and the proxy protocol summary. Base reaches session/prompt in default mode without a mode write, then receives 429 quota exhausted. Head refuses to open the session and explains that auto is unavailable; no session/prompt is sent. Both threads retain runtime_mode=auto in their respective isolated databases.
9. Stop recording; dismiss the error toast on both sides for still captures, blur the input, and capture twice at least 500ms apart until identical.

The recorded comparison proves the unsupported-Auto guard and message. Individual shell approval behavior and a successful native Auto session remain unverified because the API-key session lacks Auto and the shared model subscription returns 429 before tools execute.
