GitHub ships Gemini 4 Carbon and Claude Fable 5.2 into Copilot a day apart, with opposite admin defaults
GitHub added two frontier models to Copilot on consecutive days this week, and the two ship with opposite admin settings: one turns on by itself, the other requires a deliberate opt-in tied to a data-handling tradeoff.
What happened
GitHub made Claude Fable 5.2 generally available inside Copilot on November 9, then followed with Gemini 4 Carbon on November 10, per GitHub's changelog. Both models reach the same ten surfaces: VS Code, Visual Studio, Copilot CLI, the Copilot coding agent, the Copilot app, github.com, GitHub Mobile, JetBrains IDEs, Xcode, and Eclipse, according to GitHub's two changelog entries. Both are available to Copilot Pro+, Max, Business, and Enterprise plans, both bill at provider list pricing under usage-based billing, and both are rolling out gradually rather than appearing everywhere at once.
The difference shows up in how an organization actually gets access. Gemini 4 Carbon falls under Copilot's default model enablement: GitHub auto-enables new models unless an admin has turned off that global default or specifically blocked this one model, per the changelog. Claude Fable 5.2 works the opposite way. Enterprise and Business admins must turn its policy on themselves; it ships off, according to GitHub. The reason is spelled out in the same entry: Fable 5.2 requires data retention by default so Anthropic can run the safety classifiers that detect harmful use, and flipping the policy on counts as accepting that term. GitHub's wording is specific that retained prompts and outputs are not used to train Anthropic's models, only to operate those classifiers.
Enterprises that already run under zero data retention for other Claude models get a partial carve-out. Fable 5.2, Fable 5.1, and Fable 5 can run with zero data retention for eligible customers through the end of the calendar year, under what GitHub calls a time-bound exemption while Anthropic rolls out a system it calls Enterprise Frontier Safeguards, per the changelog. After that window closes, continued zero-retention use of those three Fable versions depends on adopting Enterprise Frontier Safeguards rather than the current exemption.
Admins now manage two new models with two different switches
An organization that wants parity between its newest model options has two separate admin tasks, not one. Gemini 4 Carbon shows up in the Copilot model picker without anyone touching a setting, as long as the org has not disabled default model enablement broadly or blocked that specific model. Claude Fable 5.2 stays invisible to every developer until an admin reads the data-retention language and explicitly turns its policy on. That is a meaningfully different bar: one model requires inaction to arrive, the other requires an administrator to sign off on a data-handling change before a single developer can select it.
The gap matters most for regulated teams that lean on zero data retention as a baseline Claude setting. GitHub's own changelog notes that every Claude model besides Fable 5, 5.1, and 5.2 continues under standard zero data retention. Those three Fable versions are the exception, and the exemption that currently covers them runs out at the end of 2026. A security or compliance team evaluating Fable 5.2 for Copilot now has a concrete expiration date to plan around, not just a feature to turn on.
Context and reactions
This is not GitHub's first back-to-back model swap this quarter. On September 3, GitHub told Copilot admins that Claude Opus 4.7 would retire October 2 in favor of Claude Opus 5. When the October 2 cutover actually landed, the replacement GitHub pointed to had changed to Claude Opus 5.5, which Anthropic had shipped on September 22, after the original deprecation notice went out. Admins who had locked their model policy to the originally named replacement had not actually provisioned the model GitHub ended up recommending.
Fable 5.2's broader launch, including a price cut to $8 per million input tokens and a disclosure that the model suspects it is being evaluated more than prior Claude releases, shipped alongside Claude Mythos 5.2 on November 9 and was covered as its own story on Pondero. The Copilot availability news is a distinct, later event: Anthropic's launch made Fable 5.2 exist, GitHub's changelog made it selectable inside the tool millions of developers already use daily.
What to watch next
Whether GitHub retires an older model to make room, matching the pattern from its August 31 and October 2 cutovers, and whether admin opt-in rates for Fable 5.2 lag Gemini 4 Carbon's auto-enabled rollout given the extra data-retention step required to turn it on.
Sources
- Gemini 4 Carbon in GitHub Copilot: GitHub changelog, primary, November 10 release notes
- Claude Fable 5.2 in GitHub Copilot: GitHub changelog, primary, November 9 release notes
- Anthropic's data retention practices for covered models: Anthropic support article, secondary, linked from GitHub's changelog
