GitHub Copilot Gets Enterprise Spend Controls: Per-User Budgets and Credit Pools by Cost Center

TL;DR: GitHub shipped two enterprise spend controls for Copilot in five days — per-user credit budgets and AI credit pools per cost center. Set them before Fable 5's cap lifts July 7.

After widespread billing-shock reports from agentic Copilot sessions, GitHub moved quickly:

Per-user credit budgets (June 30). Enterprise admins can now set a flat dollar cap per user within a cost center. Different cost centers can carry different budgets: $250/user for a platform engineering team, $40/user for everyone else. An individual user-level override takes precedence over both.

AI credit pools per cost center (July 2). A credit pool stops a cost center from consuming more than its share of the enterprise's included AI credits. GitHub calculates the pool limit automatically from the licenses assigned to that cost center and adjusts it as users join or leave — no manual number to maintain. You decide what happens at cap: block or allow overages into metered spend.

Both controls are live via the REST API; cost-center UI management is coming soon.

Why it matters: Fable 5's 50% weekly usage cap in GitHub Copilot lifts on July 7, opening full frontier-model access at token-rate pricing. If you're running agentic workflows on Copilot without spend controls set, one unmonitored overnight agent run can exhaust a month's budget. Set the per-user cap first, then layer the cost-center pool on top.

Sources: Per-user AI credit budgets — GitHub Changelog | Cost centers now support AI credit pools — GitHub Changelog | Usage-based billing for organizations — GitHub Docs