GitHub Copilot CLI: quota, live status and replies
Agent HUD follows Copilot CLI's sessions, shows when it is working and when it replies, and, once you allow it, reads your Copilot quota.
Updated 2026-10-29
At a glance
| Feature | GitHub Copilot CLI |
|---|---|
| Tokens and sessions | ✓ |
| Quota | ✓ |
| Live status | ✓ |
| Approvals | — |
| Questions | — |
| Replies | ✓ |
| One click back | — |
| Turns and calls | — |
What you see on the HUD
Each metered Copilot quota appears in the hover with its reset date, and the most used of them sets Copilot's colour in the glow. A quota that is unlimited on your plan gets no row. The plan shown is your Copilot plan.
Which account does it count against?
Your GitHub user, labelled with your login: the one the GitHub CLI is signed in to. Agent HUD reads that sign-in only after you consent in Settings. Until then, Copilot's tokens and sessions still count, without a quota.
Running turns and replies
The HUD shows Copilot CLI working, and a New reply reminder when its agent stops. The reminder comes through Copilot's completion hook, which the release adds to Copilot's settings while client hooks are on and removes when they are off. Approvals and questions stay in Copilot CLI.
What does Agent HUD read?
Copilot CLI's session events and its OpenTelemetry export, in its own folder, for tokens and sessions. For the quota, the GitHub CLI's existing sign-in, after your consent. Agent HUD launches neither gh nor Copilot, never refreshes the token and sends no message to a model.
On iPhone and Apple Watch
On the same network as the release, iPhone and Apple Watch show Copilot's quota, tokens and sessions without a subscription. Agent HUD Remote shows them on any network.