GitHub Models Fully Shuts Down July 30, 2026

GitHub announced on July 1, 2026 the definitive end of the GitHub Models platform. The playground UI, model catalog, inference API, and BYOK endpoint — every component of the service — will be decommissioned on July 30, 2026. This is not a partial capability reduction, but a complete product withdrawal.

The shutdown is unfolding in phases. In the first phase, during June 2026, GitHub already closed access to new users. The second phase, ending July 30, removes everything still active for existing users and integrations.

What Did GitHub Models Offer?

GitHub Models was a standalone service within the GitHub platform, launched as a dedicated experience for developers who wanted to explore and use AI models without a separate cloud account. The service comprised four key components:

Playground UI — an interactive in-browser interface for trying AI models with different prompts, temperatures, and parameters, without writing a single line of code.

Model catalog — a structured listing of available AI models with technical documentation and a comparative view of capabilities.

Inference API — programmatic access to models via standard HTTP requests. This component was essential for developers who embedded AI models into their own applications or automation pipelines.

BYOK endpoint — Bring Your Own Key functionality that allowed users to access third-party models through GitHub infrastructure using their own API keys.

All four components cease operation on July 30, 2026.

Affected Users and Integrations

The shutdown affects everyone using any part of the GitHub Models infrastructure — developers with applications calling inference API endpoints, teams that used the playground for model evaluation and testing, BYOK functionality users, and any automation scripts or CI/CD pipelines that depend on GitHub Models endpoints.

All active users are affected, regardless of usage level. There are no exceptions and no transitional period with limited functionality — the service shuts down completely.

Brownout Windows Force Migration

Before the final shutdown, GitHub has scheduled two brownout windows — brief, planned outages that simulate service unavailability:

• July 16, 2026 — first brownout window
• July 23, 2026 — second brownout window

During those intervals, API calls to GitHub Models endpoints temporarily return errors while the service still technically exists. The purpose is standard for platform shutdowns: developers who have not yet migrated will encounter errors in controlled conditions and be forced to start migration while there is still time to adapt.

Migration Paths

GitHub explicitly recommends two destinations:

Azure AI Foundry is the primary destination for developers who need an inference API and access to a multi-provider model catalog. Foundry offers managed endpoints, enterprise scalability, and deep integration with the Azure ecosystem. Users who called GitHub Models from code will find the smallest friction here — API access is comparable and the model catalog is broader.

GitHub Copilot is the recommended path for developers whose primary use was AI assistance within the development workflow — testing ideas, generating code, reviewing implementations. Copilot now ships with a growing number of models in the model picker and integration with VS Code, Visual Studio, JetBrains, and other popular development environments.

Strategic Consolidation

The shutdown of GitHub Models reflects a clear strategic decision: GitHub will not maintain two parallel AI experiences. The standalone inference playground and the development AI tool are being consolidated under a single umbrella — Copilot.

This move is not isolated. The same day — July 1, 2026 — GitHub announced the arrival of Kimi K2.7 Code, the first open-weight model in the Copilot model picker. Copilot is evolving from a code-completion tool into a platform for accessing diverse AI models within the development environment. GitHub Models, which tried to fill a similar space as a standalone product, lost its strategic rationale.

For complex API integrations and enterprise use, Azure AI Foundry takes over the role. For the development workflow, Copilot. For GitHub Models, there is no room left.

Timeline and Recommended Actions

Date	Event
June 2026	New-user access closed
July 16, 2026	First brownout window
July 23, 2026	Second brownout window
July 30, 2026	Full shutdown

Recommended order of action: identify all applications, scripts, and CI/CD pipelines that call GitHub Models endpoints; choose a target platform based on your needs — Azure AI Foundry for API access or Copilot for development assistance; update endpoint URLs and authentication mechanisms; test integrations and deploy changes before July 16 to avoid unexpected service interruptions.

Users who do not migrate by July 30, 2026 will face permanently unavailable endpoints with no way back.