GitHub Models Will Shut Down July 30, Including Its Playground and API
The final retirement removes the service from existing customers as well as new ones, leaving active projects with a short window to move model access or absorb failures.
GitHub Models is scheduled to shut down for every customer on July 30, removing the service's playground, model catalog, inference API and bring-your-own-key endpoints. The official retirement notice applies to existing customers with active usage, not only to people trying to start new projects.
That makes this a deadline rather than a gradual product transition. Any application that still calls the GitHub Models inference API needs a migration decision before the service disappears, and teams using the browser playground or catalog for model evaluation will lose those interfaces at the same time.
What is being removed
GitHub says the playground, model catalog, inference API, BYOK endpoints and related interface will no longer be available after July 30. The company had already closed the service to new customers in June. Its July notice extended the retirement to everyone and scheduled brief brownouts for July 16 and July 23 so users could see how their systems behave when requests fail.
The brownout dates are evidence of the intended retirement path, but the changelog does not establish that every affected workload detected those interruptions or completed a migration. Teams should verify their own logs and dependency maps instead of treating the notices as proof that they are ready.
Where GitHub points users
For projects that still need a model catalog and inference access, GitHub names Microsoft Foundry as an alternative. For AI-assisted work inside GitHub, it points users to GitHub Copilot. Those are product directions, not a promise of automatic migration, equivalent endpoints or identical model availability.
A practical migration check should identify every API key, endpoint, model identifier and test workflow tied to GitHub Models. Teams should then confirm replacement authentication, regional availability, quotas, pricing and output behaviour in the destination service. The source notice does not claim compatibility, so an endpoint swap without testing would create avoidable operational risk.
Status
Confirmed retirement schedule from GitHub. The affected surfaces and July 30 deadline are official; successful migration and compatibility depend on each customer's implementation.
Sources
Update note: Last reviewed 2026-07-28. We will revise this post if GitHub changes the deadline, service scope or migration guidance.
Sources
- GitHub Changelog — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.