GitHub Changes Copilot Governance, Retention and Billing Defaults
GitHub plans to unify several Copilot experiences and change retention, review effort and billing behavior. Enterprise administrators have decisions to make before the effective dates.
GitHub announced upcoming changes to Copilot policy and billing on August 28, 2026. The changes affect administrators because product experiences that previously had separate controls are moving under one policy.
What is scheduled to change
No earlier than September 28, GitHub plans to unify Copilot Chat on github.com, GitHub Mobile and the Copilot cloud agent. The unified experience is expected to be enabled by default. GitHub says chat data on github.com will then follow the agent-session model and be retained for the life of the account instead of 28 days.
The default effort for Copilot code review is also scheduled to move from Lite to Balanced on September 28 for organizations and repositories that leave the setting at Default. Administrators who want Lite must select it explicitly.
For Business and Enterprise customers paying by credit card or PayPal, upfront seat billing is expected to apply from the next billing cycle, with existing customers moving to the behavior on October 1. GitHub says headline plan prices are not changing.
These were announced future dates when this article was published. Administrators should confirm the live product documentation before acting.
Why it matters
A feature consolidation can change more than interface design. It can alter retention, default enablement and the scope of an enterprise policy. Those changes may affect internal privacy reviews, evidence retention, acceptable-use controls and cost forecasts.
Administrator checklist
- Review the unified cloud-agent policy before September 28.
- Decide whether account-lifetime chat retention matches company requirements.
- Set review effort explicitly if the organization should not inherit Balanced.
- Reconcile assigned seats with real users before the next billing cycle.
- Document which repositories and data classifications permit cloud-agent use.
BronzeDev view
AI coding tools should be managed as systems with data flows, identities, spend and retention—not as isolated editor plugins. Default changes are a useful trigger to inventory those controls.
Primary source
GitHub Changelog: Upcoming changes to GitHub Copilot policies and billing
