GitHub Models has been retired, according to a post by developer Simon Willison published on 9th August 2026. Willison writes that he discovered the shutdown when a GitHub Actions run for his simonw/research repository failed with the message: 'GitHub Models is temporarily unavailable as part of a scheduled retirement brownout.' He notes that message is 'already stale, because the retirement has been completed.' GitHub Models provided a model playground and a unified API across multiple LLM providers. Willison describes its biggest benefit as allowing code running in GitHub Actions to use the GitHub API key already present in that environment to execute prompts, which supported GitHub Next's 'Continuous AI' concept. Willison states that GitHub did not share the reason for the shutdown, and offers his own speculation that 'coding agent patterns made it prohibitively expensive to offer free or subsidized tokens.' His own workflow used an LLM call to generate folder summaries for a README. He reports swapping GitHub Models for an OpenAI API key with a monthly spending limit, and is now generating summaries using GPT-5.6 Luna. This report comes from a single independent source; GitHub's own reasoning has not been published.
- GitHub Models has been retired, with the retirement completed as of the 9th August 2026 post
- The service provided a model playground and a unified API across multiple LLM providers, usable from GitHub Actions via the existing GitHub API key
- GitHub did not publicly state a reason; Willison speculates subsidized tokens became too expensive
- Willison migrated his workflow to an OpenAI API key with a monthly spending limit, using GPT-5.6 Luna
What it means for you
If you built anything that quietly used GitHub Models to run AI prompts — often inside automated GitHub Actions workflows — it has stopped working. GitHub offered this as a free or subsidized way to call various AI models using credentials you already had. That convenience is gone, so those tasks now need a paid API key from a provider like OpenAI.
Try this
Search your repositories and GitHub Actions workflows for any reference to GitHub Models, and if you find one, replace it with a direct provider API key set to a monthly spending cap so a runaway job can't run up a surprise bill.
Who should care
Developers and technically-minded small teams who wired GitHub Models into automated workflows or used its playground for prototyping.
Skip this if
You've never heard of GitHub Models or you don't run automated AI tasks inside GitHub — this has no effect on you.
Sources: Simon Willison — read the original