GitHub Adds In-Product Copilot Budget Increase Requests
Members who exhaust AI credits can ask the paying account for more, while administrators retain control over the amount and approval.
Edited by Tyronne Panaino
GitHub made Copilot budget increase requests generally available on September 16 for Copilot Business and Enterprise accounts using usage-based billing. A member who reaches the available AI-credit limit can now ask the paying account for more without leaving the product flow.
The update matters to developers whose work stops at a usage limit and to administrators who manage metered Copilot spending. It adds a direct request-and-decision path, but it does not turn a budget limit into automatic approval.
What changes at the credit limit
GitHub says members were previously blocked from Copilot features that consume credits once their available AI credits were exhausted. The new flow appears at that point and lets the member submit a request for a larger budget.
The request follows the account that pays. A request against an organization-owned budget appears in the organization settings, while one against an enterprise-owned budget appears in the enterprise settings. That routing reduces ambiguity for members who may not know which administrative layer owns their allowance.
Administrators still decide the amount
Organization owners, enterprise owners and billing managers can review pending requests under the member-request area in settings. GitHub says they can approve, adjust or deny a request, and can set the new amount before selecting the approval action.
An approval updates the member budget and immediately restores access to AI credits. The documented workflow therefore shortens the path from a blocked feature to an administrator decision, while preserving the paying account's control over additional usage.
What the announcement does not establish
The release applies to Copilot Business and Copilot Enterprise under usage-based billing. The announcement does not describe an automatic approval policy, a guaranteed response time, or a universal increase for every member. Teams still need their own rules for who may approve extra usage, how much evidence a requester should provide and how requests fit existing spending controls.
The practical checkpoint is whether organizations can process requests quickly enough to avoid unnecessary work stoppages without weakening their budget review. GitHub's page documents the workflow, not its adoption rate or its effect on total Copilot spend.
Status
Confirmed. Internal confidence is medium because GitHub's official changelog supports the availability, routing, roles and access-restoration behavior, while the operational outcomes have not been independently measured.
Sources
Update note: Last reviewed September 17, 2026. We will revise this article if GitHub changes plan eligibility, routing or approval controls.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.