GitHub Copilot · AI credits reset monthly
Since June 1, 2026, GitHub Copilot runs on usage-based billing: a monthly pool of GitHub AI Credits (1 credit = $0.01 of model usage). The pool refills to full at 00:00:00 UTC on the first day of each calendar month — whether you subscribed on the 3rd or the 27th. This page tracks that reset live.
Time until next credit reset
Counts down to 00:00:00 UTC on the 1st of next month, when every Copilot plan's included AI credits refill.
Measuring the current month…
Copilot no longer counts "premium requests" for most users — it meters tokens, priced per model, paid out of a monthly credit pool. Three things decide how the reset works:
1 AI credit = $0.01 USD. Chat, Copilot CLI, cloud agent, code review, Spaces, Spark and third-party agents draw credits based on the input, output and cached tokens they consume at each model's published rate. A long agent session costs far more than a quick chat question — model choice is now a budget lever.
Your allowance resets to the full monthly amount at 00:00:00 UTC on the 1st of each calendar month. The date is fixed and does not move with your subscription billing date — renewing or paying mid-month does not refill the pool early. Unused credits are forfeited; nothing rolls over.
Inline code completions and next edit suggestions are not billed in AI credits and stay unlimited on every paid plan — even after your credits hit zero. On Copilot Free they are capped separately, at 2,000 completions per month.
Individual plans split their allowance into base credits (fixed — they match the subscription price and, per GitHub, never change) and a flex allotment (a variable top-up GitHub adjusts as model economics evolve). Business and Enterprise credits are pooled across the whole organization or enterprise, not kept per user.
| Plan | Price | Monthly AI credits | At the reset |
|---|---|---|---|
| Copilot FreeIndividual | $0 | Limited allowanceA limited AI credits allowance with models available through auto model selection only. GitHub does not publish a fixed credit figure for Free — plus 2,000 code completions per month. | Monthly limits refresh on the 1st at 00:00 UTC, same as every other plan. |
| Copilot ProIndividual | $10 / month | 1,500 total1,000 base + 500 flex. Base credits are spent first; flex applies automatically at the same rates. | Full 1,500 refills at 00:00 UTC on the 1st, regardless of your billing date. |
| Copilot Pro+Individual | $39 / month | 7,000 total3,900 base + 3,100 flex. Access to the full model catalog, including the most capable reasoning models. | Full 7,000 refills at 00:00 UTC on the 1st. |
| Copilot MaxIndividual | $100 / month | 20,000 total10,000 base + 10,000 flex — the largest individual allowance, added with usage-based billing. | Full 20,000 refills at 00:00 UTC on the 1st. |
| Copilot BusinessOrganization | $19 / user / month | 1,900 per user — pooledEvery licensed user contributes 1,900 credits to one shared pool at the billing-entity level; heavy users draw more, light users offset them. | The whole pool resets to full at 00:00 UTC on the 1st. Adding licenses mid-month grows the pool immediately. |
| Copilot EnterpriseOrganization | $39 / user / month | 3,900 per user — pooledSame pooling mechanics as Business, at 3,900 credits per licensed user per month. | The whole pool resets to full at 00:00 UTC on the 1st, independent of when licenses are billed. |
Business and Enterprise launched usage-based billing with a promotional allowance (3,000 and 7,000 credits per user) from June 1 to September 1, 2026; that promotion has ended and the standard 1,900 / 3,900 figures above now apply. The flex allotment on individual plans is explicitly variable — GitHub can change it as model pricing evolves, so budget against the base credits, not the total. Two more levers worth knowing: auto model selection earns a 10% discount on model costs on paid plans, and usage past your included credits is only possible if you (or your admin) set an additional-usage budget.
Your balance lives in GitHub's billing settings — and in your editor. These are the official places GitHub exposes it:
For individual plans: open your billing overview, then choose AI usage in the sidebar. It shows included credits used, any additional usage beyond your plan, and a per-model breakdown of what consumed them.
github.com/settings/billingGitHub's walkthrough for every plan type, including how Business and Enterprise members read their consumption under Copilot settings → Usage ("Usage this cycle").
docs.github.com/en/copilot/how-tos/manage-and-track-spending/monitor-ai-usageThe source for this page's numbers: base vs flex credits, the per-plan table, the 00:00 UTC 1st-of-month reset rule, and what happens when you exceed your included credits.
docs.github.com/en/copilot/concepts/billing/billing-for-individualsHow pooled credits work for Business and Enterprise: per-user contributions, mid-cycle license changes, pool resets, and admin policies for additional usage.
docs.github.com/en/copilot/concepts/billing/organizations-and-enterprises/usage-based-billingThe questions people actually search for when the credits run dry mid-month.
At 00:00:00 UTC on the first day of each calendar month. The date is fixed by GitHub and does not depend on when you subscribed or when your bill is charged. Unused credits are forfeited at the reset — nothing carries over. The countdown at the top of this page targets that exact moment.
The reset is 00:00 UTC, which lands at 19:00 the previous evening in New York during EST (20:00 during EDT), 16:00 the previous afternoon in Los Angeles during PST (17:00 during PDT), 08:00 the same morning in Shanghai and Singapore, 09:00 in Tokyo, and 10:00 in Sydney during AEST (11:00 during AEDT). Because the anchor is UTC itself, daylight saving never moves the UTC moment — only your local reading of it. The countdown panel above converts the next reset into your local time automatically.
No. Included AI credits do not carry over between months. Whatever is left when the clock hits 00:00 UTC on the 1st is forfeited, and the allowance resets to the full monthly amount. If you have credits to spare near month-end, that's the time to run the big refactoring agent session — not the 2nd.
No — this is the most common misconception. Paying your subscription, even mid-month right after you run dry, does not refresh the included allowance. Credits only come back at the calendar reset: 00:00 UTC on the 1st. The one exception is upgrading plans: an upgrade applies immediately, your usage from earlier in the cycle counts against the new plan's larger allowance, and you're charged only the price difference.
Features that consume credits — Chat, Copilot CLI, cloud agent, code review, Spaces, Spark — pause until the reset, unless you've set a budget for additional usage, which continues at the same per-token rates (1 credit = $0.01). Code completions and next edit suggestions keep working throughout: they never consume credits and are unlimited on paid plans. On Business and Enterprise plans, you'll see a banner offering to request more budget from your admin. Note that agent sessions are the usual culprit: one long cloud-agent run across a big codebase can consume more credits than a week of chat, because credits are priced on tokens, not prompts.
No. Inline code completions and next edit suggestions are not billed in AI credits and remain unlimited on all paid plans. On Copilot Free they are capped separately at 2,000 completions per month (Copilot Student gets unlimited completions). Only model-driven features — chat, agents, CLI, Spaces, Spark, code review — draw from the credit pool.
Base credits are fixed and match your subscription price — 1,000 on Pro ($10), 3,900 on Pro+ ($39), 10,000 on Max ($100) — and GitHub says they never change. The flex allotment is a variable top-up on top of base (500 on Pro, 3,100 on Pro+, 10,000 on Max) that GitHub adjusts as model pricing, new models, and efficiency evolve. Base credits are spent first; flex applies automatically afterwards at the same rates, everywhere you use Copilot. Practical takeaway: the flex portion can shrink in the future, so treat base credits as your guaranteed monthly floor.
Yes, they are pooled. Each licensed user contributes 1,900 credits/month on Business or 3,900 on Enterprise to a single pool at the billing-entity level — an enterprise with 100 Business users has one shared pool of 190,000 credits, so heavy users can draw more while light users offset them. Adding licenses mid-month grows the pool immediately; removing them only shrinks it at the next cycle. The whole pool resets at 00:00 UTC on the 1st, with no rollover. (A launch promotion raised these to 3,000 / 7,000 per user from June 1 to September 1, 2026; it has ended.)
Only Copilot Pro and Pro+ subscribers on an existing annual plan who stayed on request-based billing after June 1, 2026 still have premium requests — GitHub now calls this legacy billing, and there is no way to renew into it. The allowances are 300 premium requests/month on Pro and 1,500 on Pro+; they reset on the 1st of each month at 00:00:00 UTC with no carryover, extra requests cost $0.04 each, and per-model multipliers apply — since June 1, 2026, a single Copilot code review counts as 13 requests. Full details are in GitHub's legacy requests documentation.
On an individual plan, open your billing page and choose AI usage in the sidebar: included credits used, any additional usage, and a per-model breakdown. On Business and Enterprise plans, open Copilot settings from your profile menu and read the Usage card ("Usage this cycle"). In VS Code, clicking the Copilot icon in the status bar shows your progress toward your plan's limits and your reset date in place.