The News, Explained
GitHub announced general availability of Claude Fable 5.2 in Copilot on November 9, 2026, for Pro+, Max, Business and Enterprise users. Rollout is gradual, so the model may appear in eligible users’ model pickers at different times. Source
Supported surfaces include VS Code, Visual Studio, JetBrains, Xcode and Eclipse, alongside Copilot CLI, the coding agent, Copilot app, github.com and GitHub Mobile on iOS and Android. A CLI is an environment controlled by typed commands; a coding agent carries out delegated development work. Source
Business and Enterprise administrators must enable the Fable 5.2 policy in Copilot settings. It is off by default. Using the model normally involves Anthropic retaining data, including prompts and outputs, to run safety classifiers that detect harmful use. GitHub says retained data is not used to train Anthropic models. Source
Zero data retention, or ZDR, has a separate enterprise eligibility path. Eligible enterprises can use Fable 5.2, 5.1 and 5 with ZDR through the end of 2026 under a temporary exemption. Continued use after that point will require Enterprise Frontier Safeguards (EFS), according to the notice. EFS is intended to provide automated safety monitoring with options for customer-controlled storage and encryption keys. Source
Organizations must contact their GitHub account team about eligibility. GitHub Support cannot determine eligibility or enable access. Approved enterprises’ requests go to ZDR endpoints when the model is enabled, so a Business or Enterprise administrator must still turn on the Fable 5.2 policy after approval. Source
The model uses usage-based billing at provider list pricing. GitHub’s pricing table separates input, cached input, cache writes and output. A cache stores previously processed material for reuse. Costs therefore need to be assessed across the input, generated output and cache activity, even when the selected model stays the same. Source Source
OYOPICK’s Take
We welcome a broader choice of models for demanding work across development environments. For organizations, we think the useful starting point is connecting acceptable retention terms, exception eligibility and responsibility for enabling the policy. GitHub treats exclusion from training and eligibility for zero retention as separate considerations.
The enterprise exemption has a year-end deadline. Organizations using it should consider both their current approval and the later EFS transition requirements. We hope model-selection screens make the organization’s retention route and billing basis easier to understand, helping users choose expanded capabilities within their own data standards and budgets.