On August 11, Microsoft placed MAI-Code-1.1-Flash into GitHub Copilot. Microsoft's framing keyword is "small-tier coding workhorse," emphasizing high-frequency, interactive, tool-chain-heavy workflows, with the parameter sheet pushed to the background.
Running the Numbers
Microsoft AI's announcement gives several direct figures:
- Terminal-Bench 2.1 (GitHub Copilot CLI): 22% improvement;
- .NET tasks: 15% improvement;
- "Code survival rate" — generated code that makes it to commit — up 4%, with revisit rate up 9%;
- Token throughput 25% faster, and 25% fewer tokens needed for the same task;
- Vendor list price reduced to one quarter of the previous generation.
The "cheapness" has two readings. Officially, 1.1-Flash's price is one quarter of its predecessor's. Separately, GitHub's announcement says annual subscribers are billed at a 0.25x premium request multiplier — actual cost still depends on your Copilot plan and request type. Don't truncate the news to "one quarter" and assume everyone's total cost automatically drops to 25%.
Model Capability Hides in the Workflow
Vision input is the most visible change. Agents can now look at a screenshot, a chart, or an error page before deciding which code to change. It addresses part of the "context" problem: code, images, action history, and tool calls need to live in the same loop.
Improving cost and speed simultaneously is the hardest signal in this update. For ordinary chat, a lower price just saves a few dollars; for an agent that repeatedly reads files, runs tests, and opens multiple sessions in a repo, saving 25% of tokens per round compounds directly into task budgets and latency. Microsoft says the training and inference efficiency comes from hundreds of thousands of Copilot reinforcement learning environments — this "re-training on real execution traces" reads more like a product roadmap than squeezing a few points out of a static benchmark.
That said, the Terminal-Bench, .NET, and production metrics all come from Microsoft's own evaluation systems. Public materials provide no full reproduction details, context lengths, tool failure rates, or per-task-type costs. The 22% figure cannot be extrapolated to mean every coding task is 22% faster. Code survival rate is not a synonym for "better bug fixing" — it only means generated changes passed more downstream checks.
The Next Question for Coding Tools
What this really pushes is a shift in how coding models are evaluated. Model parameters still matter, but an agent's cost is determined by a chain of actions: reading the repo, drafting a plan, editing files, calling tools, checking diffs, running tests, fixing failures. Avoiding one wasted loop is worth more than answering one more interview question.
By spreading 1.1-Flash across CLI, cloud agents, IDEs, and mobile, Copilot puts a "cheap and fast" model into the same software delivery chain. It will not automatically replace high-reasoning models: complex architecture, security audits, and long-horizon migrations still need stronger models with repeated verification. The sensible division of labor is letting the small model handle the high-volume read-edit-test churn, reserving expensive models for high-risk decisions.
The next thing worth watching is whether enterprises actually wire it into fixed workflows and publicly record "how many tokens per task, how many minutes, whether failures required human handoff." Climbing a leaderboard a few more spots is the lesser story. That is the real productivity of coding agents.
Sources and verifiable links
1. Microsoft AI: MAI-Code-1.1-Flash official announcement https://aka.ms/mai-code-1.1-flash 2. Microsoft MAI-Code official repository https://github.com/microsoft/MAI-Code 3. GitHub Copilot launch announcement https://github.blog/changelog/2026-08-11-mai-code-1-1-flash-available-in-github-copilot