How many Copilot requests or AI credits do I have left?

Last updated: 26 September 2026 · Deutsch

Premium requests or AI credits

Until 31 May 2026, each Copilot chat or agent turn cost one or more premium requests, scaled by a model multiplier. On 1 June 2026, GitHub switched all plans to usage-based billing. Now a turn costs what its tokens cost: input, output and cached tokens, each priced by the model you picked. GitHub turns that sum into AI credits, and one AI credit is worth US$ 0.01.

So a quick chat question on a light model may cost a fraction of a credit, while a long agent session on a large model across many files costs far more. Credits pay for Copilot Chat, Copilot CLI, the cloud agent, Spaces, Spark and third-party coding agents. Code completions and next edit suggestions cost no credits.

How many credits your plan includes

GitHub lists these amounts for its paid personal plans:

• Copilot Pro (US$ 10 a month): 1,000 base credits plus a 500 flex allotment, 1,500 in all.
• Copilot Pro+ (US$ 39): 3,900 base plus 3,100 flex, 7,000 in all.
• Copilot Max (US$ 100): 10,000 base plus 10,000 flex, 20,000 in all.

Base credits match the price and GitHub says they never change. The flex allotment sits on top and may change as model prices shift. Copilot uses base credits first, then flex, with no setup on your side.

Copilot Free and Copilot Student also get an allowance, with models picked by auto model selection only. GitHub’s billing page names no credit figure for them. On a seat from your company, your admin’s budget sets the limit.

Where you see what is left

• Personal plan, on the web. Open github.com/settings/billing and click AI usage in the sidebar. It shows the included credits you have used, any extra usage beyond them, a chart of the models you used, and the credits and cost per model. The same numbers sit in Copilot settings under Usage.
• Company seat. Click your profile picture, then Copilot settings, and look at Usage this cycle. With a budget, it reads like “450 / 1,000 AI credits used”; without one, just the total used.
• In your IDE. In VS Code, Xcode and Eclipse, click the Copilot icon. In Visual Studio, choose Copilot Consumptions from the Copilot icon; in JetBrains IDEs, View quota usage. VS Code also shows the date your allowance resets.

GitHub notes that older IDE and extension builds may show wrong prices or usage, and names minimum versions, for example VS Code 1.120. If your IDE and the web disagree, trust the web page and update the IDE.

When it resets

At 00:00 UTC on the first day of each calendar month. The date is the same for everyone and does not follow your billing date. Unused credits do not carry over.

In Swiss or German time, that is 02:00 on the first in summer and 01:00 in winter. Your bill may fall on another day, say the 3rd, but the allowance still refills on the 1st.

What happens when it runs out

On a personal paid plan, you can upgrade, set a budget for extra usage, or wait for the next month. Code completions and next edit suggestions stay unlimited on paid plans. On a company seat, GitHub offers to ask your admin for more budget.

• Upgrade. You pay only the price gap to the next plan, and the larger allowance counts at once, including what you used earlier this month.
• Extra usage. You set a budget in US dollars; credits draw it down at US$ 0.01 each, so US$ 10 covers 1,000 credits. GitHub may cap extra usage, and you may have to pay off what you used before you can go on.

Budgets and alerts

Open github.com/settings/billing, then Budgets and alerts and New budget. A “Bundled AI credits budget” covers credits across all features; a SKU-level budget covers one, such as Copilot AI credits.

• Tick Stop usage when budget limit is reached where it is offered. Without it, GitHub only emails you when you pass the budget, and use goes on.
• Tick Receive budget threshold alerts to hear at 75, 90 and 100 per cent of the budget, by email and a banner on GitHub.

If you still have premium requests

Only for Copilot Pro and Pro+ subscribers who kept an existing annual plan. They stay on premium requests until the plan ends, then move to Copilot Free. Everyone else has been billed in AI credits since 1 June 2026.

On such a plan, the premium request counter also restarts on the 1st at 00:00 UTC. The model multipliers went up on 1 June for these plans; a Copilot code review now counts 13 premium requests.

In AI Cockpit

The Copilot card sits in the Mac menu bar window and in the app on iPhone and iPad. On Apple Watch (via the iPhone app), Copilot shows up as one line in the list of sources. You add a fine-grained GitHub token with the account permission “Plan: Read-only”; the app looks up your user name itself.

• The amount used this month, as GitHub’s billing report states it. The app asks the AI credit report first and falls back to the premium request report if that one is empty, so legacy annual plans work too.
• How much of it your plan covered, how much GitHub billed on top, and the overage in US dollars once there is any.
• The three models that used the most.
• The date the counter starts again: the first of next month, UTC.

What it does not show: how much is left. GitHub’s report lists what you used, not your allowance, so the card has no percentage and no warning colour. Compare its figure with your plan’s allowance above. The labels still say “requests”, a leftover from before June; on an account billed in AI credits, the figure is what the credit report counts.

The card counts personally paid plans only. A seat billed through an organisation or enterprise leaves GitHub’s user-level report empty; the FAQ page explains why. How the app reads the other paid services is in AI API costs at a glance.