Repository navigation
Antigravity Usage — status-bar segment disappears while toggle is checked (W28) #7809
Description
In Orca 1.4.128, the status-bar Antigravity Usage toggle can be checked while the actual Antigravity usage segment disappears from the status bar.
Status: active
Next: Port the local hotpatch into the source build and add a regression test for the status-bar visibility contract.
Source artifact: user screenshot/report from 2026-07-08; local verification reproduced against packaged renderer chunks.
Date: 2026-07-08
Scope
- Treat
antigravityas a configured usage provider for status-bar visibility, so a checkedAntigravity Usageitem renders a pending/error segment even before a fresh usage snapshot arrives. - Include
antigravityin the usage empty-state pending/configured checks. - Include
antigravity: nullin the initial rendererrateLimitsstore state so the UI has a stable provider key before the first API push. - Add a regression test covering the checked-menu-item versus visible-segment contract.
Acceptance
Done when Orca 1.4.128+ shows the Antigravity usage segment whenever Antigravity Usage is enabled and the agent is available, including the pre-refresh/pending state, and the regression test passes.
Updates
- 2026-07-08: Local hotpatch restored the visualization by adding Antigravity to provider visibility/empty-state handling and initial rate-limit state. Verification:
node --testregression against extracted packaged chunks passed locally after patching.
Activity
vadymvertyan-stack commentedon Jul 8, 2026
Manager work record, 2026-07-08:
node --testassertion against the extracted Orca 1.4.128 chunks.app.asar: Antigravity now participates in provider visibility, usage empty-state checks, and the initialrateLimitsstore shape.app.asar; kept a backup before replacement.app.asarand running the regression test against the extracted files: pass.Dispatch note: source-level implementation still needs to be ported into the Orca source build; the local installed app is patched only on this machine.
nwparker commentedon Sep 19, 2026
Draft #21678 now also covers configured Antigravity commands that PATH detection misses. Previously, a custom executable could launch and supply quota while both the usage entry and its toggle remained hidden.
In plain language: telling Orca where agy lives now keeps its usage controls available, even when automatic detection cannot find it. The user's checkbox still decides whether to show the entry.
Verified the rendered menu with an explicit renderer fixture: empty detected-agent list, a configured command, and Antigravity Usage enabled. The entry appeared; the actual checkbox hid it when unchecked and restored it when checked. Fixture/settings restored afterward. Screenshot in the PR is labeled as a fixture, not live PATH detection or populated OAuth quota.
35 gating/provider-visibility tests, renderer typecheck and changed-code quality passed. The earlier native-quota work also retains the initial/pending provider slot and independent Antigravity configuration without Gemini OAuth. No claim of Windows-specific rendering verification or release availability; keeping this issue open while the draft is reviewed.
nwparker commentedon Sep 27, 2026
Resolved by merged #21678. The status-bar usage entry and toggle remain available for configured Antigravity commands, and the checkbox continues to control visibility. The PR also covers the related quota-refresh behavior and reports passing visibility/provider tests.