GitHub Copilot · Model availability
Every time a frontier model ships, someone asks how long until it lands in Copilot. This measures the gap between a vendor’s public release and the model showing up in GitHub Copilot, across 46 launches from September 2024 to August 2026.
Lag is measured in calendar days from the vendor’s public announcement to the first date the model was selectable in GitHub Copilot (public preview counted as available).
For frontier models from major labs, the lag is usually zero. GitHub is a launch partner with Anthropic, OpenAI, and Google, so flagship models tend to appear in Copilot the same day the vendor announces them — sometimes before.
Lag shows up in two specific places: sub-variants that ship after the headline model (Codex-Max, mini tiers), and vendors GitHub isn’t a launch partner with, where integration starts only after public release.
Each point is one model launch. Anything on the zero line shipped in Copilot the same day it was announced.
Share of launches available in Copilot within N days of the vendor’s announcement.
Launch-partner status is the dominant variable. It shows up cleanly here.
| Vendor | Launches | Same day | Median | Mean | Same-day rate |
|---|
The pipeline got dramatically faster after 2024, then held steady. Since 2025 the mean has stayed in low single-digit days.
| Period | Launches | Same day | Median | Mean | Same-day rate |
|---|
Both dates are linked to their source. Sort any column; search filters model and vendor.
| Model | Vendor | Vendor release | In Copilot | Lag | Stage |
|---|
claude-opus-4-5-20251101 are training cutoffs and
do not indicate release.Take it and do something better with it: data.json · data.csv · build.py