Docs · known issues

Known issues

7 entries. Every one is a real constraint in the shipped app or an upstream limitation Dipstick cannot fix — none of them is a placeholder, and none is a promise.

Known issues, by provider
Provider Issue What to do Status
Copilot copilot_internal/user is a private endpoint and may change without notice The Copilot adapter reads copilot_internal/user, which is not a documented, versioned GitHub API. A change on GitHub’s side can make Copilot meters go stale or disappear until the adapter is updated. There is no user-side fix. The provider card distinguishes an exhausted budget, an organization policy and bad credentials, so a failure says which of the three it is. Upstream
Cursor Usage above 100 percent cannot be attributed Cursor’s payload does not identify whether usage over 100 percent is bonus capacity, credits, or on-demand billing, so Dipstick shows a cautious additional-usage warning rather than a confident figure. Check your Cursor billing page for the attribution. Dipstick deliberately will not guess. By design
Antigravity Antigravity connects but reports no meters The projection file is written by the provider’s status line. Until the official CLI emits a status-line quota payload there is nothing to project, so the provider shows as connected with no meters. Use the official CLI until it emits a payload, then choose Refresh. Refresh rereads the local projection and does not force a backend quota update. Upstream
Antigravity Gemini CLI usage has no separate provider Google retired Gemini CLI for individual and consumer accounts in June 2026 in favour of Antigravity. There is no separate provider to enable for it. Use the Antigravity provider; its gemini-weekly meter covers Gemini-model quota for Antigravity accounts. By design
All providers A meter can be dimmed and stale The last valid reading is still inside its own window, but the latest refresh did not produce a trustworthy replacement. Dipstick keeps the unexpired reading and marks it stale rather than blanking the meter or inventing a number. Hover the menu-bar item or open the popover for the bounded diagnostic. By design
All providers A selected meter does not fit in the menu bar macOS decides how many individual status items fit as the active app and available space change, so a selected meter can be hidden. DIPSTICK appears when no individual bar meters are enabled or when the selected meters do not fit. Click any visible meter to open every meter selected for the popover or menu bar, including the ones macOS hid. Open
All providers Duplicate meters after upgrading from a standalone Usage Micro app Dipstick’s installer deliberately leaves the three standalone Usage Micro apps and their preferences alone rather than removing them, so both can run at once and show the same limit twice. Quit the corresponding standalone app before opening Dipstick. By design

02 / 02 · Deliberately absent

Things that look like gaps and are not.

Adapters for two further tools exist in the codebase and are deliberately not exposed, because neither has a usable machine-readable personal quota surface to read. An adapter returns when its product ships one. They are not marketed here, and there is no page for them.

A limit that a provider does not report cannot be placed in the menu bar or the popover until it appears in a later provider response. That is not a missing feature: showing a meter for a limit nobody reported would be inventing a number.