Usage 0.29.25: Antigravity gets the quota status line, and its switch keeps

Release notes

FEATURE

Antigravity gets the quota status line, and its switch keeps it current

If you use both Claude Code and the Antigravity CLI, the panel's existing status line (the readout at the bottom of a terminal) switch now puts the same quota display on Antigravity too. Machines without Antigravity remain untouched: no folder or file is created. On macOS it places a hook (a small program triggered by an event) in ~/.gemini/antigravity-cli/ and runs it with built-in /usr/bin/python3, independent of the app's virtual environment. Think of fitting matching dashboards to two cars: your existing dashboard is backed up first and restored when you turn the switch off. The new script stays behind so a CLI already starting does not collide with its deletion and show an error for its whole session. Startup replaces a missing or outdated script only while the switch is on. pip and uv installs now include it; non-macOS platforms leave Antigravity settings alone, avoiding /usr/bin/python3 on Windows.

BUGFIX

A brief burst no longer marks you Heavy

After you send one especially large message, the status display will no longer rush to label you Heavy. Burn rate (the pace calculated by dividing tokens, units of AI text processing and billing, by elapsed time) used to use a span as short as one minute. Cache creation from one message could therefore push the rate high on its own. The shortest span is now five minutes, matching the forecasting floor already used by burn_rate.py. It is like judging speed from a car's gauge: you cannot call someone a speeder from one hard press at the starting line; you need a short stretch of road. Usage is not hidden; a brief spike is simply less likely to attach a heavy-user label.

FEATURE

Two menu toggles now sit together without a misleading divider

When you open the menu to adjust its two toggles, they now appear as one group, with the separator between them removed. Both were always simple on/off controls, but the line was like splitting matching side dishes into separate sections of a menu: it suggested they had different roles. No new control has appeared, and neither toggle does anything different. The layout now matches their actual relationship. Seeing two switches side by side tells you they are both options you can turn on or off independently, without making you guess what distinction the divider was meant to signal.

Original changelog

Original changelogAntigravity gets the quota status line, and its switch keeps it current

**The status line switch now covers the Antigravity CLI too.** The panel's single switch has always installed Claude Code's status line; it now mirrors the same quota display onto Antigravity when its CLI is installed. The hook is copied to `~/.gemini/antigravity-cli/` and runs under macOS's built-in `/usr/bin/python3`, so it stays stdlib-only and independent of the app's virtual environment. A status line you configured yourself is backed up to a sidecar file first and restored when the switch is turned off; the deployed script is deliberately left behind, because deleting it races with any CLI that is starting and would leave that session showing a status line error for its whole lifetime. A machine without the Antigravity CLI is untouched — no directory and no file is created, and the switch keeps working for Claude Code exactly as before.
**Startup self-healing keeps the Antigravity status line current.** Installing it only on the switch's rising edge would have hidden the feature from everyone whose switch was already on, and would have frozen the deployed script at whatever version first installed it. Self-heal now reinstalls it when it is missing and re-copies it when its bytes differ from the bundled source, both gated on the switch being on — so turning the switch off keeps it off. The Antigravity branch is isolated from the rest of self-heal and only records a log entry when the install actually succeeds.
**`pip` and `uv` installs ship the Antigravity hook.** `usage_statusline_agy` was missing from `py-modules`, so a non-bundle install could not resolve the script and the switch silently did nothing for Antigravity.
**Non-macOS platforms no longer touch Antigravity's settings.** The Windows tray shares the same toggle, and `~/.gemini/antigravity-cli/settings.json` expands there too, so a Windows user with the CLI would have had `/usr/bin/python3` written into their configuration. The sync is now a no-op off macOS.

Original changelogA brief burst no longer marks you Heavy

**A short burst no longer classifies you as a heavy user.** Burn-rate classification divided tokens by an elapsed span as small as one minute, so a single message's cache-creation tokens could produce a rate high enough for Heavy on their own. The minimum span is now five minutes, matching the forecast floor `burn_rate.py` already used.

Original changelogTwo menu toggles now sit together without a misleading divider

The menu's two toggles are grouped together without the separator that used to sit between them; both are plain on/off switches, so the divider implied a distinction that does not exist.