# Antigravity host-sleep comparison

Base: 57db750b8f379d6656ad774b11bb6039094ca873
Head: 808b3d0bea6bc394c343e2244c7ce567452c8a7a

Each side ran `T3CODE_DEV_SEED=0 vp run dev` in its own detached worktree,
with an isolated, newly migrated database and the same Gemini API endpoint
provided through GOOGLE_GEMINI_BASE_URL. No source or timeout constants were changed.

Browser: Chromium, 1280 x 800, light theme. Antigravity 1.5.12,
Gemini API key sign-in, Gemini 3.8 Flash, Low reasoning.

UI steps on each side:
1. Pair the browser to that dev server.
2. Settings > Providers > Add provider > Antigravity > Next > Next.
3. Select Gemini API key, supply a non-empty test key, Add instance, Connect.
4. Confirm Authenticated and select Gemini 3.8 Flash in a new default-project thread.
5. Hide the thread details panel, start browser recording, and send this exact prompt:

   Without using any tools, write directly in your reply a very long, detailed essay (at least 5000 words, numbered sections) on the history of lighthouses.

6. When response text is visibly streaming, identify the server PID from its listening
   port and verify its working directory is the correct checkout.
7. Run `python3 freeze.py SERVER_PID 960 freeze.jsonl`.
   The driver recursively collects the server descendants (including `agy acp` and
   the keep-awake helper), sends SIGSTOP to all of them, waits 960 real seconds,
   and sends SIGCONT. The browser and Vite keep running.
8. Observe the same thread after wake, retaining the recording through the outcome.

Head freeze began at 23:04:31.331Z on 2026-11-19.
Base freeze began at 23:07:04.020Z on 2026-11-19.

Uploaded videos redact the host label in the reconnect banner only; the
transcript and turn outcome are retained. Freeze timing logs accompany the driver.

## Observed results

Head resumed at 23:20:31.349Z after 960.018 seconds. Its run completed at
23:20:35.542Z, and the app rendered the full essay through section 14 and its
conclusion without the inactivity error.

Base's sleeping driver received SIGTERM before its finally block ran. The retained
server tree was resumed manually at 23:23:29.598Z after 985.578 seconds (16m26s).
At 23:23:30.659Z the server logged orchestration-v2.acp-prompt-inactive,
driver antigravity, timeoutMillis 900000. The run failed at 23:23:32.920Z.
The browser stayed reconnecting until Retry now was clicked; its post-reconnect
recording shows the same partial essay ending mid-sentence and the 15-minute
provider error. The base recording is supplied in two parts with a roughly
9-second gap between them, after the server had already failed the run.

The final still on each side was checked against a second screenshot at least
500ms apart with ImageMagick pixel comparison: zero changed pixels.

Limitations: this uses SIGSTOP/SIGCONT, as in triage, rather than a physical OS
suspend. It does not prove the genuinely-silent-awake timeout or an exact fresh
15-minute post-wake silence window. Real replies differ in wording.
