September 1, 2026: Copilot policy rollout and agent workflow updates

Good morning. It is September 1, 2026, and GitHub’s most important fresh signal is not a dramatic launch, but a cluster of small operational changes that matter to anyone managing Copilot at scale.

First, the product surface is getting more capable. In GitHub Copilot for VS Code, the August release adds agent-session controls like side conversations, portable agent plugins, model switching inside Claude sessions, and the ability to continue Copilot or Claude sessions that began in other apps. That is a practical step toward treating Copilot less like a single chat box and more like a task environment that can move across tools.

Second, the policy and billing rollout begins today. GitHub says it is reenabling Copilot Business and Copilot Enterprise signups for credit card and PayPal buyers, and new buyers must pay before getting seat access. Existing card and PayPal customers move to the new billing behavior on October 1, and GitHub says list prices stay unchanged. At the same time, GitHub says Copilot Chat on GitHub.com, Copilot Chat in GitHub Mobile, and Copilot cloud agent will converge no earlier than September 28 into a single experience. It also says chat history will be retained for the life of the account, and Copilot code review defaults are shifting from Lite to Balanced.

For admins, the other key change is model governance. GitHub’s global model policy for generally available Copilot models is being enforced gradually through September 1. Unconfigured GA models inherit the default policy, while open-weight models and models that require data retention are disabled by default. That sounds abstract, but it matters because model choice is no longer just a developer preference. It is becoming an enterprise control plane.

The current model menu also matters. GitHub’s docs list GA options including GPT-5.6 variants, Claude Opus 5, Claude Sonnet 5, MAI-Code-1.1-Flash, Kimi K2.7 Code, Kimi K3, Grok 4.5, and Grok 4.6. The retirement history shows September 1 retirement dates for Claude Opus 4.5 and 4.6, Claude Sonnet 4.5 and 4.6, Gemini 3.1 Pro, and Raptor mini. So the practical question today is not just what GitHub offers, but which of those models remain selectable under the new default policy on each surface: GitHub.com, Copilot CLI, VS Code, and enterprise settings.

There is also a useful billing plumbing change for enterprise teams. GitHub Apps can now access enterprise billing data with read or read-write permissions. That means finance and BI workflows can pull usage, budgets, and cost-center data without depending on one individual owner token. In plain language, it makes the billing automation less fragile. If one person leaves or changes permissions, the data connection does not have to break with them.

That billing point matters because Copilot is not a simple seat-only product. GitHub’s billing engine meters AI work in credits. A short prompt can burn little, while a long agent session can cost much more because the model and token usage drive consumption. So when GitHub changes when seats activate, when defaults switch, or when models are available by policy, it can change how teams experience cost even if the sticker price does not move.

On operations, the status page now shows the August 27 Copilot AI Model Providers incident and the August 27 GitHub Billing disruption as resolved, with updated timestamps in late August and today. That means the live question is not whether those incidents are still ongoing. The open question is whether GitHub publishes a clear postmortem or hardening note that explains what happened and what it changed.

Microsoft’s latest explicit scale disclosure remains the July 29 earnings call, where it said GitHub Copilot has 50 million users, GitHub has 225 million users, paid Copilot seats are over 30 million, and Copilot revenue accelerated over 60 percent quarter over quarter. Those are Microsoft-reported figures, not independently audited GitHub revenue, but they remain the best current scale marker from the parent company.

There is one more security thread worth keeping in view. GitHub’s July 28 supply-chain security work shipped multiple mitigations across npm and GitHub Actions, including read-only protections for high-impact npm accounts, safer checkout defaults for pull_request_target, workflow-trigger controls, read-only Actions cache for untrusted triggers, staged publishing, and an Actions network firewall preview. That does not eliminate supply-chain risk, but it narrows some common attack paths in package publishing and CI workflows.

So the day’s picture is straightforward. GitHub is tightening model policy, changing Copilot billing entry points, and making the agent workflow more portable, while recent billing and model-provider incidents are now marked resolved. The unresolved question is what the policy rollout does in practice.

What to watch next: whether docs or screenshots show exactly which Copilot models remain selectable after September 1, whether GitHub publishes a postmortem for the billing and model-provider incidents, and whether the promised unified Copilot experience arrives on or after September 28 with any admin controls or opt-out path.