Hide untouched Antigravity model families - #2924
Conversation
Drop a quota family from menu cards and widgets when no lane reports known usage; keep every family when all are untouched; pair an unfamiliar family's lanes by title so a reset lane never hides beside an active sibling; keep provider details listing every family as the diagnostic surface.
Co-authored-by: Urda <github@urda.com>
Co-authored-by: Peter Urda <peter.urda@gmail.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. |
|
Codex review: needs maintainer review before merge. Reviewed August 14, 2026, 4:23 AM ET / 08:23 UTC. ClawSweeper reviewWhat this changesThe branch hides Antigravity model families whose quota lanes are all known zero from menu cards and widgets, while retaining unknown-usage and provider-detail rows. Merge readinessKeep open for normal owner review. The PR’s shared compact-display rule matches the provider’s known/unknown quota semantics and leaves diagnostic provider details unfiltered; no patch defect was found. Priority: P3 Review scores
Verification
How this fits togetherAntigravity quota summaries enter CodexBar as named usage windows, then feed menu-card metrics and widget rows. This change adds a shared presentation-only filter for compact surfaces while the provider-details pane continues to show every reported lane. flowchart LR
A[Antigravity quota summary] --> B[Named usage windows]
B --> C[Family visibility rule]
C --> D[Compact menu card]
C --> E[Widget rows]
B --> F[Provider details]
F --> G[All reported lanes]
Before merge
Agent review detailsSecurityNone. Review metrics
Root-cause clusterRelationship: Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. Merge-risk optionsMaintainer options:
Technical reviewBest possible solution: Land the centralized compact-display filter after normal merge validation, retaining the documented title fallback for new provider bucket families and all lanes in provider details. Do we have a high-confidence way to reproduce the issue? Yes — current main renders every quota-summary window in both compact paths, and a snapshot with one active family plus one known-zero family reaches the proposed filter deterministically. This read-only review did not execute the app. Is this the best way to solve the issue? Yes — centralizing the rule avoids menu/widget drift and its known-usage condition matches the provider parser’s contract; preserving provider details is the appropriate diagnostic fallback. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against f043a784a71f. LabelsLabel justifications:
EvidenceWhat I checked:
Likely related people:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
Rating scale
Overall follows the weaker of proof and patch quality. Workflow
History |
|
Thanks for making this built in! |


Replaces #2875 (fork disallows maintainer edits) — the contributor's commits are preserved verbatim with @urda as author, plus one correction on top.
Summary
Antigravity's
RetrieveUserQuotaSummaryreports every model family the plan covers, so an account that only runs Gemini still carries Claude/GPT rows pinned at 0% that crowd out real lanes (especially the small widget's 2-row limit). Display surfaces (menu card, provider settings usage list, widget) now hide a family once every lane in it reports known zero usage.Correction over #2875
The original hid a family whose usage was unknown (nil) as if it were known-zero.
AntigravityQuotaFamilyVisibilitynow requiresusageKnownbefore treating a lane as idle, so a family that simply hasn't reported yet keeps rendering. The all-untouched fallback (never render an empty card) was already correct and is preserved.Proof
make checkclean; fullmake test859/859 selections greenFixes the dead-row half of the Antigravity display complaints; ranked menu-bar selection is unaffected (untouched families never win there anyway).