GitHub Copilot Changes in September: Fewer Credits, Longer Chat Retention, Pricier Default Reviews

Short answer: GitHub has three Copilot changes landing within a few weeks, and they affect cost, data retention, and review defaults rather than just adding new features.

For Copilot Business and Enterprise customers, the most important dates are:

• September 1, 2026: existing customers’ temporary higher AI-credit allowances end, while self-serve Business and Enterprise sign-ups begin reopening for credit-card and PayPal customers.
• No earlier than September 28, 2026: Copilot Chat on GitHub.com, GitHub Mobile, and Copilot cloud agent begin converging into one experience and policy. GitHub says GitHub.com chat data will then be retained for the life of the account instead of 28 days.
• September 28, 2026: repositories and organizations that leave Copilot code review on Default move from Lite to Balanced review effort.
• October 1, 2026: existing Business and Enterprise customers paying by credit card or PayPal begin moving to the updated upfront seat-billing behavior at their next billing cycle.

None of this means Copilot Business or Enterprise list prices are increasing. GitHub says the seat prices remain $19 per user per month for Business and $39 for Enterprise. The practical problem is that the same configuration can still become more expensive or retain data for much longer if an admin leaves the defaults untouched.

Feature and pricing check: August 29, 2026. GitHub’s August 28 announcement says some rollout dates are “no earlier than” September 28, so exact launch timing may move. Recheck the linked GitHub documentation before changing production policy.

The four changes at a glance

The useful way to treat this is not as one product announcement. It is a configuration migration with three separate controls: spending, retention, and code-review effort.

1. The first September change is easy to miss: included AI credits shrink

GitHub moved organization and enterprise Copilot plans to usage-based billing earlier this year. Existing customers received a temporary higher allowance for the first three months, from June 1 through September 1, 2026.

That promotional period is now ending.

GitHub’s current documentation lists these standard monthly allowances:

One AI credit is currently priced at $0.01 when additional usage is billed.

The important detail is that organization and enterprise credits are pooled, not isolated per user. For example, 100 Business seats contribute a standard pool of 190,000 credits per month. Heavy users can consume more than 1,900 if other users consume less.

That flexibility is useful, but it can hide the September change. A team that comfortably stayed inside a 300,000-credit promotional pool with 100 Business seats now has only 190,000 included credits at the same seat count.

A simple September budget test

Before September starts, calculate:

last 30 days of AI credits ÷ September standard pooled allowance

For a 100-seat Business organization:

• Standard pool: 100 × 1,900 = 190,000 credits
• If August usage was 250,000 credits, the same usage pattern would exceed the standard pool by 60,000 credits.
• At the current $0.01 overage rate, that would represent up to $600 of additional usage if paid overage is allowed and consumption does not change.

This is not a forecast of the bill—models, token usage, and user behavior vary—but it is a much better warning signal than waiting for the first September invoice.

GitHub’s docs also say additional paid usage is enabled by default for organizations and enterprises. If the goal is a hard ceiling rather than uninterrupted service, an admin needs to configure the relevant paid-usage policy or budgets deliberately.

2. GitHub.com Copilot Chat is moving from 28-day retention to account-lifetime retention

The biggest non-financial change is the new unified Copilot experience.

GitHub says that no earlier than September 28, Copilot Chat on GitHub.com, Copilot Chat in GitHub Mobile, and Copilot cloud agent will relaunch under a single experience and policy.

The announcement explicitly says:

• the unified experience will be enabled by default after launch;
• GitHub.com will migrate fully to the agent-sessions experience;
• GitHub.com chat data will be retained for the life of the account instead of 28 days, aligning with the existing cloud-agent experience.

That is a major policy difference for teams that currently treat GitHub.com chat as relatively short-lived conversational data.

What “life of the account” does not automatically tell us

It is important not to stretch the announcement beyond what GitHub actually says.

The August 28 changelog does not say that every Copilot surface, IDE chat, or local session suddenly receives identical retention. The stated convergence specifically names GitHub.com, GitHub Mobile, and Copilot cloud agent.

GitHub’s current cloud-agent documentation also says cloud-agent sessions can be archived but not deleted, while local sessions from tools such as Copilot CLI, VS Code, JetBrains, or the Copilot app can be deleted under their respective session controls.

That makes retention policy worth reviewing before the unified experience becomes the default, especially for organizations that have internal rules about how long prompts, generated responses, code context, or investigation notes may remain accessible.

It also means “archive” should not be assumed to mean “delete.” Archiving is primarily a visibility and organization action.

3. Opting out has a bigger consequence than simply keeping the old interface

GitHub says organizations can opt out of the unified Copilot experience.

But opting out is not a way to preserve the current GitHub.com and Mobile experience indefinitely. According to the August 28 announcement, teams that opt out will lose access to Copilot on GitHub.com and GitHub Mobile after the new experience launches.

So the decision is closer to:

• accept the unified experience and its policy; or
• disable that GitHub.com/Mobile path for the team.

GitHub recommends Business and Enterprise administrators review the policy before September 28.

For security and compliance teams, the right question is therefore not “Do we like the new UI?” It is:

Are account-lifetime GitHub.com chat records compatible with our internal data-handling rules, and if not, which Copilot surfaces should remain approved?

4. Copilot code review’s default changes from Lite to Balanced

The same September 28 date also changes how Copilot code review behaves when a repository or organization leaves its review effort on Default.

Today, GitHub documents two review levels:

• Lite: faster, targeted review for common bugs, vulnerabilities, and style issues.
• Balanced: routes the pull request to a higher-reasoning model for longer analysis of complex logic, security-sensitive code, and cross-service changes.

Starting September 28, GitHub says the Default value will resolve to Balanced rather than Lite.

If an organization or repository explicitly chooses Lite before then, GitHub says that selection will be respected and will not be switched.

Why this matters for cost

GitHub’s current code-review documentation gives these estimated AI-credit cost ranges per review:

The published Balanced range is five times higher at both endpoints, but that does not mean every Balanced review costs exactly five times more. GitHub says consumption depends on pull-request size, custom repository instructions, and the models involved.

Still, the default change matters enormously for repositories that automatically request Copilot review on every pull request.

A rough planning formula is:

monthly automatic reviews × average cost per review

If a team runs 500 automatic Copilot reviews per month, even a modest increase in average review cost can become a meaningful part of the shared AI-credit pool.

There can also be a secondary cost: GitHub says Balanced reviews may consume marginally more GitHub Actions minutes than Lite reviews.

5. New seat billing is stricter even though seat prices stay the same

GitHub says it will begin reopening self-serve Copilot Business and Enterprise sign-ups on September 1 for customers paying by credit card or PayPal.

For those new self-serve customers:

• each new seat assignment requires payment before the user receives Copilot access;
• mid-cycle seat additions are still prorated from assignment through the end of the billing cycle;
• revoking a seat does not create a prorated refund;
• the removal is reflected in the next monthly billing cycle.

For existing credit-card and PayPal Business/Enterprise customers, GitHub says the updated upfront seat-billing behavior begins October 1, 2026 at the start of the next billing cycle.

The list price is unchanged, but seat hygiene becomes more important because removing an unused assignment mid-cycle does not recover that month’s charge.

That makes monthly access reviews more valuable, especially in organizations with contractors, interns, rotating teams, or short-lived projects.

A practical admin checklist before September 28

The safest response is a small audit rather than a blanket Copilot shutdown.

1. Recalculate the September AI-credit pool

Use the standard allowances, not the June–August promotional values:

• Business: 1,900 credits per seat
• Enterprise: 3,900 credits per seat

Compare the result with actual August usage.

2. Decide whether paid overage should remain enabled

If unexpected AI spend is unacceptable, do not rely on the included pool alone. Review GitHub’s paid-usage policy and budget controls before the promotional allowance disappears.

3. Review GitHub.com and Mobile retention with security/compliance

Document whether account-lifetime retention is acceptable for the kinds of prompts developers currently put into Copilot on GitHub.com.

Do not assume the old 28-day behavior continues after the unified experience launches.

4. Make code-review effort explicit

If routine pull requests do not need Balanced review, set Lite explicitly at the organization or repository level before September 28.

If security-sensitive or cross-service repositories benefit from deeper analysis, leave those repositories on Balanced intentionally rather than receiving it accidentally through Default.

5. Audit automatic review volume

Count how many pull requests automatically request Copilot review each month. Multiply that by realistic observed credit consumption once effort-level metrics are available.

This is more useful than budgeting from the maximum published range alone.

6. Review assigned seats before October billing

Identify seats that belong to inactive users, temporary collaborators, or teams that no longer need Copilot. Revoking after a cycle begins will not create a prorated refund.

A better policy pattern: separate “allowed” from “default”

The September changes reveal a recurring problem in AI administration: a feature can be allowed without needing to be the default everywhere.

A practical policy might look like this:

This avoids two bad extremes: disabling useful AI features everywhere, or letting every new default quietly become organization policy.

What is confirmed, and what is still uncertain

Confirmed by GitHub

As of August 29:

• Business remains $19/user/month and Enterprise $39/user/month.
• Standard included AI credits are 1,900 and 3,900 per user respectively.
• The higher promotional allowances end around September 1.
• GitHub.com chat retention is scheduled to change from 28 days to the life of the account under the unified experience.
• Default code review effort changes to Balanced on September 28.
• Explicit Lite selections will remain Lite.
• Existing card/PayPal customers move to the updated assigned-seat billing behavior starting October 1.

Still worth rechecking

• The exact launch day of the unified experience: GitHub says no earlier than September 28, not a guaranteed September 28 launch.
• Real-world Balanced review credit consumption for a particular codebase.
• Any additional deletion, export, or retention controls GitHub documents as the unified experience rolls out.
• Whether organization-specific compliance or data-residency configurations alter the practical impact for a particular enterprise.

Conclusion

GitHub’s September Copilot changes are easy to misread as routine product consolidation. They are really three operational changes arriving together:

1. less included usage after the promotional credit period;
2. much longer GitHub.com chat retention under the unified agent experience;
3. a more expensive review mode becoming the default unless admins choose Lite explicitly.

The best preparation is simple: recalculate the credit pool, review retention policy, make code-review effort explicit, and clean up assigned seats before the new billing cycle.

That turns September from a surprise invoice or compliance discussion into a controlled configuration change.

Sources

Checked August 29, 2026:

• GitHub Changelog — Upcoming changes to GitHub Copilot policies and billing
• GitHub Docs — Usage-based billing for organizations and enterprises
• GitHub Docs — About billing for GitHub Copilot in organizations and enterprises
• GitHub Docs — About GitHub Copilot code review
• GitHub Docs — Managing agent sessions
• GitHub Docs — Getting started with budget controls