Agent HUD · Guides · Supported clients
GitHub Copilot CLI quota on Mac
Copilot is the one client whose quota reading is off until you turn it on, because reading it needs your GitHub sign-in.
At a glance
| Quota | Metered quotas, after consent |
|---|---|
| Account | GitHub user, login label |
| Running · completion | Yes · agent-stop hook |
| Credentials read | Existing GitHub sign-in, after consent |
What you see
One row per metered quota the service reports, each with its own reset date; free accounts use their own limits. Windows that are unlimited, or that carry no entitlement, have no row at all. The plan is your Copilot plan.
How the account is named
Your GitHub user, labelled with your login. Without a usable token the rows stay unresolved rather than being guessed at.
Running turns and completions
Running turns are detected; completions arrive through the agent-stop hook.
What Agent HUD reads
Copilot's session events and its OpenTelemetry export. Its database and the editor or desktop-app stores are never read. Quota reading stays off until you confirm a dialog that names the sources it will use, and the dialog is shown every time you switch it on.
Common questions
- Why do I see no Copilot quota?
- Quota reading is off until you confirm it under Settings → Agents → GitHub Copilot. Local activity and token counts work without it; only the quota rows need your GitHub sign-in.
- What happens if I switch it off again?
- The account, its rows and its quota history are forgotten. Turning it back on starts again from a fresh reading, and the consent dialog is shown once more.
Last updated: 2026-09-20 · The behaviour described here is documented in full, with the code it comes from, in Agent HUD Open. providers.md