The Temporary AI Allowance Nobody Turned Off: GitHub Budgets Can Now Expire on Their Own (from 1 Sept 2026)

Why this matters: most runaway AI bills are not caused by heavy use. They are caused by a temporary allowance nobody switched back off.

The pattern is familiar. Someone is on deadline, so their limit gets raised for the week. The project ships. Nobody reverts it. Three months later the invoice explains what happened.

The feature GitHub made generally available on 2026-09-01 targets exactly that: a budget assigned to one person can now carry an expiration date, and GitHub removes it when that date arrives.

1. What a “budget” is here

In GitHub’s billing settings, a budget is a spending ceiling you draw yourself. The documentation lists the scopes:

• Personal account: the whole account, or a specific repository
• Organization: the whole org, or a single repository
• Enterprise: the whole enterprise, a single organization, a single repository, a cost centre, or an individual user

Three types exist: product-level (Codespaces, say), SKU-level (a specific feature), and an AI credits budget spanning all AI-related features.

2. The part people misread: going over does not necessarily stop anything

Worth confirming before you rely on it. The documentation is explicit:

• At 75%, 90% and 100%, GitHub sends email notifications and shows a banner.
• Without the stop-usage option enabled: “you will be notified by email if you exceed your budget, but usage will not be stopped.”
• With it enabled: usage halts once you pass the budget.

Plainly: the default is a warning, not a wall. If your actual goal is preventing a surprise invoice, you have to tick the stop option — the assumption that “a budget exists, therefore we are safe” is where teams get caught.

3. The new part: three expiry options

The shipped feature applies to individual user budgets, with three choices:

What happens at expiry? GitHub states the budget is removed and the person falls back to their cost centre budget or the universal budget — not to no limit at all, but to the line they were on before.

You set this in billing settings, and GitHub notes it can also be set through the Budgets REST API via the expires_at field, with the date changeable or clearable at any time.

4. Who can set one

The documented roles: personal account holders, organization owners, enterprise owners, and billing managers. Ordinary members neither see nor change these.

5. Availability

• Generally available: 2026-09-01.
• Plans: GitHub Copilot Business and Copilot Enterprise.

GitHub’s own rationale is blunt: previously, every temporary budget override had to be removed by hand, which at enterprise scale turned into recurring cleanup work.

6. A small-team playbook you can copy

1. Set one global AI credits budget at the number you can genuinely accept per month.
2. Decide on the stop option: tick it if a surprise bill is the bigger risk; leave it off if blocking someone mid-deadline is worse — but then someone must actually read those three warning emails.
3. Give every temporary bump an expiry date — next billing cycle for short bumps, a specific date when the end is known.
4. Record the expiry date in whatever tracks the request, because when it lapses the person quietly drops back to their old limit and will otherwise just feel that something “got slower”.

7. What this article does not claim

• Per-seat pricing for Copilot Business or Enterprise. Our sources are the changelog and billing docs; no prices are cited here — check the official pricing page, unverified.
• Whether free or individual plans get this. The announcement names Business and Enterprise only; nothing else is stated, and we do not extrapolate.
• Whether admins receive a separate notification at expiry. Not documented on the pages read — unverified.
• The full list of features covered by an AI credits budget. Described as spanning “all AI-related features” without an itemised list — unverified.

Official links

• GitHub Changelog (source for the feature and availability date): https://github.blog/changelog/2026-09-01-set-an-expiration-date-for-individual-user-budgets/
• GitHub billing docs, set up budgets (source for scopes, thresholds and permissions): https://docs.github.com/en/billing/tutorials/set-up-budgets

Related reading

• GitHub Copilot tool page (plans and free-tier verification log)
• The 1 September Copilot AI credits cliff: which side are you on?
• How Copilot’s per-model token rates are calculated