One tool, several models: GitHub quietly ends the single-vendor assumption
At Universe on 29 October 2024, GitHub made Copilot multi-model. The interesting part is not the models. It is that choosing one became a setting.
At GitHub Universe on 29 October 2024, GitHub announced that Copilot becomes multi-model: developers can choose between Anthropic’s Claude 3.5 Sonnet, Google’s Gemini 1.5 Pro and OpenAI’s models, including o1-preview and o1-mini, inside the same product.
Copilot was the flagship example of a tool built on one supplier. That it now offers a choice, from a company owned by Microsoft, is a signal worth reading.
What actually changed
Not the capability. The architecture of the decision.
Until now, picking a tool meant picking the model underneath it, permanently and invisibly. Multi-model support separates the two. The tool is the thing you buy; the model becomes a setting you can change when a better or cheaper one appears.
GitHub also previewed Spark, a way to build small applications by description rather than by code. Interesting, early, and secondary to the point above.
Why this matters outside software development
Because the same pattern is coming to the tools your office actually uses.
Different models are genuinely better at different jobs. A reasoning model is worth its cost for a complex contract comparison and is wasteful for reformatting an address list. Being able to route each task to an appropriate model is not a technical nicety; it is the difference between an AI budget that scales and one that surprises you.
It also softens the dependency problem. When the model is a setting rather than a foundation, a price change or a service problem at one provider stops being an existential event for your workflow.
The question to start asking vendors
From now on, add one line to every software evaluation: can we change the model behind this, and what happens to our data when we do?
Most vendors in late 2024 will answer no. That is fine, and it is still worth knowing. A no tells you that your contract with that vendor is also, silently, a contract with their supplier — and that you should read both.
This is the direction of travel. Tools that let you choose will win procurement conversations in 2025, not because choice is fashionable, but because it is the only honest answer to « what happens when this gets more expensive? »