GitHub Models is retired: your free AI endpoint is gone
GitHub Models was fully retired July 30 — playground, catalog, inference API and BYOK. What a shut-down model endpoint teaches you about portability.
As of yesterday, GitHub Models is gone. GitHub's changelog confirms the full retirement on July 30, 2026: the playground, the model catalog, the inference API, and bring-your-own-key. Not deprecated, not read-only — removed, for every customer including the ones with active usage. If a workflow of yours called that endpoint, it started failing yesterday. The GitHub Models retirement is worth five minutes of your attention even if you never used it, because of how the ramp ran.
What actually happened
GitHub telegraphed this properly, which is the part to study. The product closed to new customers on June 16. The full retirement notice landed July 1 with two scheduled brownouts on July 16 and July 23 — deliberate short outages so teams would discover their dependency before the hard cutoff instead of after it. Then July 30, everything off.
The suggested landing spots are Microsoft Foundry for a broad model catalog, or GitHub Copilot if you want models inside GitHub itself. Neither is a drop-in for a free inference API you were hitting from CI.
That's a clean, well-run sunset. It's also a thirty-day window between "this is going away" and "this is gone," for an endpoint that was trivially easy to wire into an Action.
Why a retired model endpoint matters for your business
Free inference bundled into a platform you already pay for is the most seductive integration there is. No new vendor, no new invoice, no procurement conversation. It's also the integration with the least protection — nobody signed anything, so nobody owes you a migration path.
Watch how these things get load-bearing. Someone prototypes a PR summarizer against a free endpoint. It works. Six months later it's classifying support tickets, and the base URL is hardcoded in three workflow files that nobody has opened since. There was never a decision to depend on it.
The fix is boring and takes an afternoon: every model call goes through one adapter in your own code. One module that owns the base URL, the key, and the request shape; everything else calls your function, not the vendor's. Swapping providers becomes a config change and a diff in one file instead of an archaeology project. Same discipline as never scattering raw SQL through a codebase — you already know this pattern, you just have to apply it to the model layer.
Then go grep. github.ai, models.inference, any base URL that isn't yours. Do it before the next sunset notice, not during one.
Key takeaways
- GitHub Models was fully retired July 30, 2026 — playground, catalog, inference API and BYOK, for all customers
- The ramp: closed to new customers June 16, retirement notice July 1, brownouts July 16 and July 23
- Suggested alternatives are Microsoft Foundry or GitHub Copilot; neither is a drop-in for a free CI inference endpoint
- Free bundled endpoints get load-bearing without anyone deciding to depend on them
- Route every model call through one adapter you own, so a provider swap is a config change
We build the model layer so the provider is a setting, not a rewrite. One adapter, your keys, your logs — swap OpenAI for Anthropic for a local model without touching your product code. See how we build vendor-agnostic systems.
Sources: GitHub Changelog — GitHub Models is now retired, GitHub Changelog — full retirement notice, GitHub Changelog — closed to new customers.
- #github
- #ai-models
- #portability
- #developer-tools
- #vendor-risk
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
North Korea behind the debug and chalk npm hijacks
Amazon links the debug, chalk, and axios npm supply chain attacks to a DPRK group. One incident hit 1 in 10 cloud environments in two hours. Audit your dependencies.
Read it30+ Minnesota water utilities hit in coordinated OT attack
More than 30 Minnesota water utilities were hit in a coordinated OT attack on July 26-27. What internet-reachable controllers mean for your business.
Read it