GitHub Copilot budget increase requests are now generally available, and admins approve them from settings

GitHub announced on 16 September that its Copilot budget increase requests are generally available. Until now, a member who used all of their allotted Copilot AI credits was simply blocked from any Copilot feature that consumed credits. The new flow adds a request path at the moment they hit the limit, and an approval path for admins that lives inside settings.

The flow, from either side

For the member, the block screen now carries a button to request more budget. GitHub says the request routes automatically to whichever account pays for the budget. If a member sits under an organization-owned budget, the request appears in that organization's settings. If they sit under an enterprise-owned budget, the request appears in the enterprise's settings. The member does not have to guess which admin owns their spend.

For the admin, the section is called "Requests from members" and the roles that can act on it are organization owner, enterprise owner, and billing manager. GitHub's post says an admin reviews the request, sets an amount, and clicks Approve and increase. That single action updates the member's budget to the amount the admin chose and immediately restores their access to AI credits. The admin can also adjust the requested amount before approving, or deny the request.

What plans it applies to

The feature is available on GitHub Copilot Business and GitHub Copilot Enterprise, and only under usage-based billing. Teams still on legacy fixed-seat pricing do not get this flow, because there is nothing to request more of. A team that hits a credit ceiling on the personal Copilot Pro plan is a separate question that GitHub's post does not address.

Where the time savings come from

The specific thing this replaces is a message a developer sends to whichever colleague controls a shared card, describing what they were doing, why the ceiling was reached, and how much more spend they need. Two things go wrong with that. The developer stops for however long that message takes to answer, which on a Friday afternoon can be a Monday morning. The admin has no context about which credit pool the ask lands against, so the answer is either a full approval or a rejection with follow-up questions.

The GA version handles both parts. The request carries the identity, the pool, and the current usage. The admin sees a queue rather than a single message thrown over the wall. The approval is instant, so a developer who was blocked at 15:47 is unblocked at 15:48. And because the audit trail lives in GitHub's settings, a finance team gets a record of which increases were approved by whom, at what amount, and for which member.

Source

Primary source: Copilot budget increase requests are generally available, GitHub Changelog, 16 September 2026.