GitHub Models Will Fully Retire on July 30 as Developers Move to Alternatives

GitHub will fully retire GitHub Models on July 30, 2026, completing a shutdown process that began when the service closed to new customers in June. The change applies to every remaining customer, including teams and developers that still have active usage.

What will stop working

According to GitHub's official announcement, the retirement covers the GitHub Models playground, model catalog, inference API and bring-your-own-key endpoints. The related user interface will also be removed. Applications or internal tools that depend on those endpoints therefore need a replacement before the cutoff rather than treating the change as a cosmetic product update.

GitHub plans two brief brownouts before the final shutdown. Requests will temporarily return errors on July 16 and July 23, giving maintainers an opportunity to identify workloads that still rely on the service. Teams should use those windows as operational checks, but they should not wait for a brownout to begin inventorying API calls, secrets, deployment variables and fallback behavior.

Migration options

GitHub points developers toward Azure AI Foundry when they need access to a broad model catalog. For AI-assisted development inside GitHub workflows, the company recommends GitHub Copilot. Those products are not direct drop-in replacements for every GitHub Models integration, so maintainers should compare authentication, model identifiers, request formats, rate limits and billing before changing production traffic.

The practical next step is to locate every use of GitHub Models, select an alternative provider, test equivalent prompts and outputs, and remove obsolete keys after migration. Monitoring should remain enabled through July 30 so that overlooked calls are visible before the endpoint disappears permanently.

Sources

• github.blog

Cover image: dumbledad, source, licensed under BY.