[Bug]: Gemini models through Antigravity do not report context window usage #15291

Activity

1. arhammahajan

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Oct 3, 2026
2. arhammahajan

   changed the title [-][Bug]: `Gemini models through Antigravity do not report context window usage` ```markdown ```[/-] [+][Bug]: Gemini models through Antigravity do not report context window usage[/+] on Oct 3, 2026
3. juliusmarminge commented on Oct 3, 2026

   

   juliusmarminge

   on Oct 3, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   Triage

   Thanks @arhammahajan for the report and the screenshot, and for separating this from the Usage page. The empty ring comes from the Antigravity runtime this nightly installs, not from the composer dropping a field.

   What's happening

   • The context-window indicator only renders when the setting is on and the active thread has a usage snapshot. For Antigravity, that snapshot comes from an ACP usage_update (used / size), or from an idle state_update that includes usage. AntigravityAdapter doesn't invent a window of its own, and with no snapshot the ring is left out rather than showing an "unavailable" state. Your screenshot (Gemini 3.5 Flash (Low), no ring next to the model picker) shows that empty state.
   • The managed runtime pinned in apps/server/src/provider/antigravityRelease.ts is agy_acp_server_1.1.1. That build tracks token totals internally but has no client usage_update send path.
   • The ACP registry's current agent is 1.3.0 (published 2026-10-02). It does send session/update with sessionUpdate: "usage_update", used, and size, and lists gemini-3.5-flash-low with a 1,048,576-token window, so a 1.3.0 runtime should supply what the composer already knows how to show.
   • This is separate from subscription quota on the Usage page (open PR feat(antigravity): report subscription usage limits #15198).

   Likely fix area

   • The pinned Antigravity release in antigravityRelease.ts (moving to a runtime that sends usage_update).
   • Separately, whether the composer should show an explicit "not reported" state when a provider never sends usage, as you suggested.

   A protocol capture is only needed if your Binary path setting points at a different agy_acp_server than the managed 1.1.1 install. A maintainer will decide on the fix direction.
4. juliusmarminge

   added

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   and removed

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Oct 3, 2026