Copilot · GitHub Copilot premium requests menu bar
Copilot premium requests, against the clock
Dipstick resolves your own gh executable and runs one fixed read-only request — gh api --include copilot_internal/user --hostname github.com — to read the Chat, Code Completions and Premium Requests quotas your account reports. copilot_internal/user is a private GitHub endpoint and may change without notice; GitHub CLI supplies its own authentication, so Dipstick never reads or stores your token.
Copilot · Premium Requests Example reading
Usage 55% Window 30% Ahead
Limits Dipstick can show
- Premium Requests
- The quota people actually run out of.
- Chat
- Shown when the account reports it.
- Code Completions
- Shown when the account reports it.
Unique to Copilot
Premium requests are metered per month against a plan allowance, which makes Copilot the provider where a mid-month glance is worth the most and the hardest to get from GitHub’s own surfaces.
Because gh owns the credential, enabling Copilot in Dipstick grants the app nothing it did not already have on your machine.
If a quota comes back marked unlimited or unavailable, Dipstick hides it rather than drawing a full bar, because a full bar is a claim.
02 / 06 · Mechanism
How the reading is taken
Dipstick reads your own gh executable. Here is exactly what happens on each refresh.
Dipstick resolves the user’s own gh executable and runs exactly one fixed read-only request: gh api --include copilot_internal/user --hostname github.com, with a minimal environment, bounded output, a deadline, cancellation and child cleanup.
--include prints the response headers ahead of the body. They are read for one narrow purpose: telling GitHub’s three different 403s apart — an exhausted request budget, an organization policy, and bad credentials — and reading the retry-after and x-ratelimit-reset values that set the retry delay.
The adapter hashes the returned login for account continuity and projects only the plan, the monthly reset, and the known Chat, Code Completions and Premium Requests quota snapshots. Limits marked unlimited or unavailable stay hidden rather than being drawn as full.
03 / 06 · Stated here, not buried
copilot_internal/user is a private GitHub endpoint
copilot_internal/user is a private GitHub endpoint. It is not a documented, versioned API, and it may change without notice. If it changes, the Copilot meters can go stale or disappear until the adapter is updated — that is a real risk and it is stated here rather than discovered later.
This is also why the Copilot adapter reads response headers: GitHub returns three materially different 403s through the same door, and a meter that cannot tell "budget exhausted" from "your organization disabled this" would be worse than no meter.
04 / 06 · Scope
What is never read or stored
GitHub CLI handles its existing authentication, so Dipstick never reads or stores the GitHub token; the returned login is hashed for account continuity and the raw response is not persisted or logged.
Across every provider, credentials, raw responses, transcripts, account identifiers and local paths are not persisted or logged, and usage readings are not persisted at all unless you turn on local history. The privacy page lists this field by field →
05 / 06 · One product
One app, one download, five providers
This is not a Copilot edition. It is the same application and the same download as the other four pages below, and the $2 unlock covers every one of them.
06 / 06 · Start
Set up and start reading
GitHub CLI installed and signed in to an account with Copilot access. Confirm with `gh auth status` before enabling the provider.