The Antigravity desktop app (2.26.0, Windows 11, Ryzen 7 5800H with Radeon graphics, 32 GB) feels sluggish while an agent is working, and it gets worse over a long session. I measured where the time and memory go. All numbers are from Windows process counters and Chrome DevTools metrics on the running app.
The “Working” animation
While an agent works, the conversation shows a shimmering “Working” label and a spinner. The shimmer animates -webkit-mask-position, which the browser cannot hand to the GPU compositor, so the page restyles and repaints on the main thread every frame. Over 10 minutes the window process averaged 60% of one CPU core and about 85 style recalculations per second, while JavaScript itself took under 4% of the time.
I paused the page’s animations for 16 seconds and turned them back on:
| Window process CPU | GPU process CPU | Main thread busy | Style recalcs per second | |
|---|---|---|---|---|
| Animations running | 14.6% | 32.4% | 21.3% | 58 |
| Paused | 2.0% | 21.0% | 8.6% | 4 |
| Running again | 18.9% | 55.8% | 32.8% | 88 |
So most of the window’s work during agent runs is decoration. Typing and scrolling wait behind it. Moving the shimmer to transform or opacity, pausing it when the window is not focused, and honouring the reduced-motion setting would remove most of this.
Memory of the language server
On 25 October I sampled every process once a minute for 3 hours while one conversation was open and working:
| Time | language_server.exe private memory | Threads | Handles |
|---|---|---|---|
| 16:10 | 326 MB | 64 | 966 |
| 17:00 | 1,840 MB | 79 | 1,147 |
| 18:00 | 2,643 MB | 83 | 1,200 |
| 18:50 | 2,912 MB | 89 | 1,282 |
| 19:10 | 2,716 MB | 87 | 1,290 |
It gives memory back now and then, but each low point is higher than the one before (358, 1,690, 2,124, 2,310 MB), so what it keeps grows by roughly 12 MB a minute. On an earlier day the same process had reached 12.96 GB after about two days. I can’t tell from outside whether this is a leak or a cache without a limit. The conversation was active the whole time, so I have no idle period to compare.
Long conversations
The window’s JavaScript memory stayed flat (78 to 106 MB), so the page code is not leaking. But the number of elements on the page doubled over the 3 hours, from 4,118 to 8,299, and the number of finished fade-in animations still attached to elements grew from 541 to 1,285. Every step of the conversation seems to stay on the page with its animation attached, so each restyle has more to do as the conversation gets longer. Rendering only the visible part of the conversation would keep this flat.
Background disk work
While the agent ran, ~\.gemini\antigravity\agyhub_summaries_proto.pb (759 KB) was replaced as a whole 6 times in 90 seconds, for a net change of minus 6 bytes. That is 4.5 MB written to record a few bytes. The conversations folder also had 372 leftover -wal files (210 MB) for 500 databases, some about 14 times the size of their database, and the open conversation’s WAL stayed at 33 MB during the run.
I can share the raw samples if they help.