By ByteBot
GitHub published a changelog entry on August 28 that most Copilot Business and Enterprise users will miss until it hurts. Three changes land before October 1 — a 37–44% cut to monthly credit allowances, an upfront billing model that charges seats before users get access, and a unified experience that extends data retention from 28 days to the life of your account. Each has a hard deadline. None are optional.
Your Credit Allowance Is Shrinking on September 1
The promotional credit pools GitHub introduced when it launched usage-based billing in June 2026 expire on August 31. Starting September 1, monthly allowances reset to standard levels:
- Copilot Business: 3,000 → 1,900 credits per user per month (37% reduction)
- Copilot Enterprise: 7,000 → 3,900 credits per user per month (44% reduction)
Subscription prices remain unchanged at $19 or $39 per user per month. You pay the same amount and receive significantly less included usage. GitHub framed the promotional window as a “transition period” to help teams establish baselines — but many teams used those three months to build workflows around allowances they are about to lose.
The problem is predictability. Developers in the GitHub community report consuming 52% of monthly tokens in a single day, and one team of three burned 65,000 tokens in five days. Agentic sessions are the main driver: Agent mode generates roughly 60 times more input tokens than output tokens because it crawls files and retries code generation on every call. If your team leaned into agentic coding over the summer, September 1 is going to feel abrupt.
Balanced Code Review Becomes the Default on September 28
This is the change most likely to slip through unnoticed, and it will affect anyone using Copilot’s code review feature.
Currently, new repositories and organizations default to Lite reviews — quick feedback using a lighter model. On September 28, the default flips to Balanced. Balanced reviews use a higher-reasoning model that analyzes the full repository context rather than just the diff, consume more credits, run longer GitHub Actions jobs, and require larger runners that bill at higher per-minute rates.
If you do not explicitly set your preference to Lite before September 28, your review costs will increase automatically with no action on your end. For organizations with Copilot code review enabled on every pull request, this is a meaningful and silent budget increase. You can preserve Lite by selecting it explicitly in organization settings → Copilot → Copilot code review before the deadline.
Copilot Chat, Mobile, and Cloud Agent Merge Into One Product
Also on September 28, GitHub will consolidate Copilot Chat on github.com, Copilot Chat in GitHub Mobile, and the GitHub Copilot cloud agent into a single unified product governed by a single policy.
The key policy change within this consolidation: chat data retention extends from 28 days to the lifetime of your account. GitHub’s cloud agent already retained data indefinitely; this aligns the web and mobile products to the same standard.
For individual developers, this is unlikely to matter. For enterprises with data governance policies, legal teams need to review this before September 28. Opting out is all-or-nothing — disabling the unified experience removes Copilot access from github.com and GitHub Mobile entirely. There is no partial opt-out.
Upfront Seat Billing Starts October 1
Existing customers face a final change on October 1: GitHub shifts to an upfront model where seat assignments require payment before users gain access. Previously, charges appeared at the start of the next billing cycle. Going forward, adding a seat means paying for it immediately. Seat revocations mid-cycle remain non-refundable.
Finance teams managing large seat counts need tighter controls. The grace period that allowed provisional seat assignments without immediate cost is going away.
Three Actions Before September 28
Based on the official GitHub changelog, here is your checklist:
- Baseline your credit usage now. Pull current consumption from your GitHub billing dashboard before August 31. If you are already near 1,900 (Business) or 3,900 (Enterprise) credits per user per month, September 1 will trigger overages. Configure spend controls and set up alerts.
- Set your code review default explicitly. Go to organization settings → Copilot → Copilot code review and select Lite before September 28 if you want to preserve current cost behavior. Every repository without an explicit setting will inherit the new Balanced default.
- Involve legal or compliance before September 28. Lifetime chat retention is a material policy change for regulated industries. Understand whether opting out is necessary for your organization — and that opting out removes github.com and Mobile Copilot access entirely.
The promotional honeymoon is over. GitHub gave teams three months to adjust, and September 1 is where the real economics of usage-based billing begin. Teams that planned ahead will absorb the transition. Teams that did not are about to get a much clearer picture of what their Copilot usage actually costs.
