Build1 publisher2 min readPublished
Copilot Pro's AI Credits reset at 00:00 UTC on the 1st, whatever day the subscriber pays
GitHub resets Copilot Pro's included AI Credits at 00:00 UTC on the 1st of each month, so paying mid-month does not refill a used-up allowance. Teams that forecast usage by invoice date are tracking a different clock from the one GitHub meters them on.
The Engineer · Build desk
What happened
- GitHub Copilot replaced its premium requests system with a usage-based AI Credits model on June 1, 2026.
- A GitHub Community user, raymastech, upgraded to Copilot Pro, ran out of credits, paid again mid-month and found the allowance still empty.
- A dev.to write-up of the thread sends affected users to Settings, Billing and licensing, AI usage, where an export shows first consumption time, included credits, additional usage and billing entity.
- The same write-up recommends managing Copilot at the organization level instead of on individual developer accounts, so usage is easier to see.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- constraint Once the allowance runs out early in a month, it stays empty until the 1st, so the timing of a heavy week decides how long a developer goes without included credits.
- decision Teams that budget Copilot by invoice date have to forecast against the UTC calendar month instead and reconcile it with the invoice separately.
- exposure Usage nobody remembers can come from an unknown app, token or session, so the AI usage page is also a place to look for a compromised account.
- contradiction The write-up's own example does not match its stated reset rule, so plans should follow the 1st-of-month rule and ignore the example.
The reset date is fixed, so how much an early burn costs depends on how early it happens. A dev.to write-up of the problem says GitHub resets the included allowance at 00:00 UTC on the 1st of each calendar month, whenever the payment or renewal happens [3]. Take a 30-day month. If the allowance runs out at the end of the 5th, the developer has 25 days without included credits. Renewing on the 15th does not shorten that wait [1][2].
The post's own example gets this wrong. It describes a team that uses up its August credits, pays again in mid-September and then has to wait until October 1 [5]. Under the rule the same post states, August usage would have reset on September 1. The example only works if it was the September allowance that ran out [2].
I think a calendar reset is a reasonable design. One UTC reset for every account is simpler to meter and to explain than a separate anniversary date for each subscriber. The cost of that simplicity falls on whoever forecasts Copilot usage from invoice dates. The rule as reported covers the $10 Copilot Pro plan [2]. The post does not say whether seats billed through an organization or enterprise reset on the same date.
The forum thread behind the post contains a second problem, and the calendar does not explain it. The user, raymastech, wrote that the credits showed 100% used "when I didn't use it for a second" [6]. The dev.to author lists misattribution, background usage or a compromised account as possible causes [7].
The usage export can narrow that down. If the first consumption timestamp is earlier than any session the developer remembers, the question is no longer billing but who had access [8]. The post's next check is whether an organization or enterprise also assigns Copilot to the user, and which entity is selected for billing [9]. After that, it suggests checking Settings > Applications and Developer settings for unfamiliar authorized apps or tokens, and the security log for unusual sessions. Anything unknown should be revoked, and the post warns against posting reports or receipts publicly while doing it [10].
What to watch
- GitHub documentation or a statement on whether Copilot seats billed through an organization or enterprise reset on the same 00:00 UTC calendar date.
- A GitHub reply in raymastech's Community thread explaining the usage the user says they never generated.
- Any change from GitHub that lets a mid-month renewal restore included credits.