Check Copilot in VS Code or GitHub.
- Confirm the GitHub account in your editor. Use the account that owns the personal subscription or assigned seat.
- Open the Copilot status-bar dashboard in VS Code. Read the available AI-credit or legacy-request usage, completions and period labels.
- Check the same identity on GitHub. Open personal Settings → Billing and licensing and the available Copilot/AI usage view. GitHub’s monitoring guide distinguishes personal and organization routes.
Interface labels can vary with plan and rollout. If a menu differs, start from the official guide rather than using an unrelated organization metrics page.
Read the account’s actual unit.
| Type | How to read it |
|---|---|
| AI credits | The current credit-based allowance can contain base and flex components. Read the applicable credit pool and additional spending in GitHub; credits are not a message count. |
| Legacy premium requests | Some accounts remain on request-based terms. Model and feature multipliers affect consumption. Read the account’s actual billing mode before using an old request-count example. |
| Code completions | A completion allowance can appear separately. Read its label and whether it is limited or unlimited for the account. |
| Organization usage | Business and Enterprise budgets, adoption metrics and reports need the appropriate organization role. A personal remaining percentage cannot substitute for those reports. |
A usage reset can differ from the payment date.
GitHub’s individual credit-based billing guidance describes a calendar-month allowance refreshing on the first day at 00:00 UTC. That is not necessarily your subscription charge date. Legacy request-based allowances also need their own displayed period checked; organization rules and plan transitions can differ.
For example, 00:00 UTC is 08:00 in UTC+8. Convert the displayed time to your own zone before calling a reset late. A date change in the editor does not establish that new usage data has arrived.
Check supported Copilot readings on iPhone.
- Choose GitHub Copilot in TokenVive Settings. Open the official authorization page and enter the current device code when requested.
- Complete authorization for the intended account. Return to TokenVive, inspect the available usage groups and select a period.
- Read the unit and update time. Compare the same account, allowance and time in GitHub before comparing with a phone or Watch reading.
TokenVive handles supported remaining-usage fields returned for the account, including legacy premium-request/chat/completion fields and a credit-labelled field when the provider returns it. New AI-credit coverage has not yet been verified against a live account in this guide. Use GitHub for the complete current credit balance, model charges and paid overage settings.
Copilot message counts, token analytics and organization reports are not available in TokenVive. AI connections and refreshes require active TokenVive membership or remaining trial access. Sign-in and reconnection stay on iPhone; opening both paired apps syncs credentials for supported Watch queries. iOS 17 / watchOS 10 or later are required.
Missing, blocked or different from the editor?
- Match the GitHub identity, personal/organization context and billing mode first.
- Compare used with remaining only for the same pool and period. An unlimited field is not a numeric 100%.
- Check the last successful update. Missing data stays unavailable rather than becoming zero. Reconnect on iPhone when requested.
- For a blocked editor request, distinguish allowance exhaustion from temporary rate limits. Review GitHub’s notice and spending settings there; TokenVive does not add credits or unblock requests.
Sources and dates
Official guidance was read November 12–15, 2026. This guide was prepared November 16. Plan rollouts and the account’s own usage view determine current eligibility. TokenVive is an independent app.