Startups5 min read

GitHub Copilot's September 2026 Reset: Prepaid Seats and One Agent

GitHub's August 2026 changelog sets three September changes: prepaid Copilot seats from 1 September, credit pool reductions from 3,000 to 1,900 per user, and a unified Chat and cloud agent experience.

GitHub Copilot's September 2026 Reset: Prepaid Seats and One Agent

Three Changes in One Changelog

GitHub published a changelog on 28 August 2026 announcing a set of policy and billing changes taking effect throughout September 2026. The changes fall into three distinct categories: how Copilot seats are purchased, how promotional AI credits are counted, and how the various Copilot interfaces are presented to users. Together they represent GitHub's most substantial revision to Copilot's commercial model since the product reached scale, and they close the promotional access period that many engineering organisations have been operating within.

Prepaid Seats From 1 September

From 1 September 2026, GitHub is reenabling sign-ups for new Copilot Business and Enterprise customers paying by credit card or PayPal. Alongside this, all new seat assignments for both tiers now require upfront payment before users gain Copilot access. Under the previous model, seats could be assigned and developers could begin using Copilot immediately, with the charge applied at the end of the billing cycle. Under the prepaid model, the cost is incurred at the moment of assignment. For existing customers on credit card or PayPal billing, the prepayment requirement applies from the start of their next billing cycle beginning on or after 1 October 2026.

Procurement Implications for Engineering Teams

The shift to prepaid seats changes how teams manage Copilot access at an operational level. The previous model allowed flexible seat assignment: a developer could be given access when starting a project and the seat cost appeared in the next billing summary. Under the prepaid model, access and cost are simultaneous, which makes seat assignment a more deliberate financial decision. Teams that have been assigning seats opportunistically — giving access on request and allowing unused seats to lapse at billing close — will need to move to a more managed allocation approach. For Indian IT services firms running Copilot across variable-headcount project teams, this is particularly material: each seat assignment now has an immediate balance-sheet effect rather than a deferred billing adjustment.

Credit Pool Reductions

From 1 September 2026, promotional AI credit pools for Copilot Business and Enterprise customers drop to standard levels. The Business promotional pool decreases from 3,000 credits per user to 1,900, and the Enterprise promotional pool decreases from 7,000 credits per user to 3,900. Teams that have been using Copilot AI features at promotional credit volumes will find their available monthly capacity reduced. This matters for organisations that have built workflows consuming AI credits at the higher promotional rate — agentic code reviews, large-context summarisation, Copilot Extensions. Teams hitting the new standard ceiling will need to reduce usage, optimise workflows for credit efficiency, or budget for additional credit purchases.

A Unified Copilot Experience From 28 September

No earlier than 28 September 2026, GitHub plans to merge three currently separate Copilot interfaces into a single unified experience: Copilot Chat on github.com, Copilot Chat in the GitHub mobile app, and the GitHub Copilot cloud agent. The three surfaces currently have separate user interfaces, separate policy configurations, and separate administrative controls. The post-merge experience will have a single shared interface and a single policy governing all three entry points. From an administrative standpoint this simplifies governance: teams managing Copilot access across web, mobile, and agent contexts currently maintain three separate configurations; after the merge, one policy covers all surfaces. For end users, the consolidation means session context can carry across interfaces without manual re-entry.

Code Review Default: Balanced Replaces Lite

GitHub is changing the default effort level for Copilot's automated pull request code review from Lite to Balanced. Balanced reviews examine more of the diff and surface a broader range of findings compared with Lite. Teams that adopted Copilot code review for its speed at the Lite setting should expect more comments per pull request at the Balanced default. The change raises the quality floor of automated review: Balanced output is closer in depth to a human reviewer's first pass, which makes Copilot's review more useful for quality assurance but also increases the signal volume that developers need to evaluate before merging.

What This Means for Teams in India

September 2026 marks the end of the promotional Copilot environment that many engineering organisations have been operating within. The combination of prepaid seats and reduced credit pools requires more active management of Copilot usage at both team and organisation level. For Indian software development and IT services companies that deployed Copilot broadly during the promotional period, the transition involves reviewing seat counts, auditing current credit consumption against the new standard limits, and revising procurement workflows to account for the prepayment requirement. The unified agent experience arriving on 28 September will simplify governance for teams managing Copilot across multiple surfaces. Teams should complete their policy review and seat audit before the end of September to avoid service interruptions when the changes take full effect.

The Bottom Line

GitHub's 28 August 2026 changelog announced three September 2026 changes to Copilot. From 1 September, new seat assignments require upfront payment and sign-ups for Business and Enterprise resume; promotional credit pools drop to standard levels (Business: 3,000 to 1,900; Enterprise: 7,000 to 3,900 per user). From no earlier than 28 September, Copilot Chat on github.com, Copilot Chat in mobile, and the cloud agent merge into a single unified experience under one policy. The code review default shifts from Lite to Balanced, increasing the depth of automated PR reviews. For engineering teams operating at scale, the transition from promotional to standard commercial terms is the most consequential change and requires deliberate seat and credit planning.

Frequently Asked Questions

What changed about GitHub Copilot seat assignment from 1 September 2026?+

From 1 September 2026, all new Copilot Business and Copilot Enterprise seat assignments require upfront payment before users gain Copilot access. Under the previous model, seats could be assigned and developers could begin using Copilot immediately, with the charge applied at the close of the billing cycle. Under the new prepaid model, the cost is incurred at the moment of seat assignment. For existing customers paying by credit card or PayPal, the prepayment requirement applies from the start of their next billing cycle beginning on or after 1 October 2026. GitHub simultaneously reenabled sign-ups for new Copilot Business and Enterprise customers from 1 September.

How much did GitHub reduce Copilot credit pools in September 2026?+

From 1 September 2026, promotional AI credit pools for Copilot Business and Copilot Enterprise customers dropped to standard levels. The Copilot Business promotional pool decreased from 3,000 credits per user per month to the standard 1,900, a reduction of 1,100 credits per user. The Copilot Enterprise promotional pool decreased from 7,000 credits per user per month to the standard 3,900, a reduction of 3,100 credits per user. Teams that built agentic workflows or large-context summarisation pipelines at the promotional credit level will find their available monthly capacity reduced, and teams exceeding the new standard limits will need to purchase additional credits or optimise usage.

What is the unified Copilot experience GitHub announced for September 28, 2026?+

No earlier than 28 September 2026, GitHub plans to merge three currently separate Copilot interfaces into a single unified experience: Copilot Chat on github.com, Copilot Chat in the GitHub mobile app, and the GitHub Copilot cloud agent. The three surfaces currently have independent user interfaces, separate policy configurations, and separate administrative controls. After the merge, a single shared interface and a single unified policy will govern all three entry points. For administrators, this reduces Copilot governance from three separate configurations to one. For end users, session context can carry across web, mobile, and agent interfaces without manual re-entry.

What does the shift from Lite to Balanced code review mean for teams?+

GitHub changed the default effort level for Copilot's automated pull request code review from Lite to Balanced. Lite reviews are faster and produce a smaller number of targeted findings. Balanced reviews examine more of the diff and surface a broader range of findings per pull request. Teams that adopted Copilot code review primarily for its speed and low comment volume at the Lite setting should expect more review comments per PR at the Balanced default. The shift means Copilot's code review is now deeper by default — closer in scope to a human reviewer's first pass — which increases its usefulness for quality assurance but also means more signal that developers must evaluate before merging. Organisations can configure a different default at the organisation or repository level.

Work with us

TechPillow builds custom software development for teams across India and beyond.

Explore
TT

Written by

TechPillow Team

Sharing insights on technology, product development, and the Indian tech ecosystem.

Ready to Build Something Extraordinary?

From ideation to launch, we're your end-to-end technology partner.

Book a Free Strategy Call