GitHub Models Retires July 30: Migration Guide

GitHub Models — the free playground and API GitHub launched for testing AI models without leaving GitHub.com — shuts down completely on July 30, 2026. The playground, model catalog, inference API, and bring-your-own-key (BYOK) endpoints all go away on that date, and GitHub has already run two scheduled brownouts, on July 16 and July 23, 2026, specifically to flag code that still depends on the service before it disappears for good.

The shutdown timeline

GitHub announced the retirement in stages rather than all at once:

• June 16, 2026: New organizations and enterprises with no prior GitHub Models usage lost access outright, on both free and paid GitHub plans. Existing customers with active usage were unaffected at this point.
• July 16 and July 23, 2026: GitHub ran short, scheduled brownouts — deliberate service interruptions — so teams could find hidden dependencies on GitHub Models before the real shutdown.
• July 30, 2026: Full retirement. The playground, model catalog, inference API, and BYOK endpoints stop working, and the related UI is removed from GitHub.com.

If your team still calls https://models.github.ai/inference — whether from application code, a GitHub Actions workflow, or a prototype script — that integration breaks the moment the July 30 cutoff passes.

What developers are actually losing

GitHub Models was popular specifically because it was free to prototype against, gated only by a personal access token with models:read scope and tiered rate limits rather than a billing account. GitHub's own documentation lists limits like 15 requests per minute and 150 requests per day for lower-tier models, and 10 requests per minute and 50 requests per day for higher-tier ones, with production-grade limits unlocked only after opting into paid usage. That free, no-credit-card sandbox is what disappears — not just one product surface, but the entire no-cost path GitHub offered into frontier and open-weight models.

Migrating to Azure AI Foundry

GitHub's own retirement notice points developers who need continued model access toward Azure AI Foundry (documented in places as Microsoft Foundry, Microsoft's newer name for the same platform). The practical migration is smaller than it sounds: according to Microsoft's own upgrade guide, you don't need to change your application logic, only the endpoint and key.

# Before: GitHub Models (free tier, GitHub PAT auth)
client = ChatCompletionsClient(
    endpoint="https://models.github.ai/inference",
    credential=AzureKeyCredential(github_pat),
)
 
# After: Azure AI Foundry (paid, deployed-model auth)
client = ChatCompletionsClient(
    endpoint=foundry_deployment_endpoint,  # from Models + endpoints tab
    credential=AzureKeyCredential(foundry_api_key),
)

Both use the same Azure AI Inference SDK shape, so the swap is a configuration change: deploy the model you were testing in Azure AI Foundry, copy the endpoint and API key from the deployment's overview page, and update your environment variables. The difference that matters for planning is billing — Azure AI Foundry is pay-as-you-go against an Azure subscription, not free.

Or move the workload into GitHub Copilot

For teams whose GitHub Models usage was really about AI-assisted coding workflows rather than general API access, GitHub's second suggested path is GitHub Copilot, which now bills per-token through GitHub AI Credits rather than the old premium-request model. That's a better fit if the underlying need was IDE-integrated chat or agent sessions instead of programmatic model calls from a separate service.

Migration checklist before July 30

1. Grep your codebase and CI configs for models.github.ai, models.inference.ai.azure.com (an older, already-deprecated endpoint), or any GitHub PAT scoped to models:read.
2. Treat the brownout windows as your test plan — if a July 16 or July 23 brownout already broke something silently, that's a dependency you still need to migrate.
3. Decide between Azure AI Foundry and Copilot based on whether the integration is programmatic API access (Foundry) or developer-facing chat and agent workflows (Copilot).
4. Budget for the switch from free to paid. Neither replacement path preserves GitHub Models' no-cost rate-limited tier — factor Azure consumption or a Copilot seat into your team's tooling budget now, not after July 30.
5. Update GitHub Actions workflows separately from application code — CI jobs that called GitHub Models for tasks like automated PR summaries or test generation need the same endpoint and credential swap.

Teams building AI coding agents on top of GitHub Models specifically should prioritize this migration: agentic workflows tend to be the highest-volume callers, and they're exactly what hits GitHub Models' tightest per-minute rate limits first once the free tier is gone entirely rather than just capped.