Microsoft's MAI-Code-1-Flash Beats Claude Haiku 4.5 by 16 Points at 60% Fewer Tokens
Microsoft's first in-house coding model ships inside GitHub Copilot, beating Claude Haiku 4.5 by 16 points on SWE-Bench Pro while using 60% fewer tokens

- Microsoft's first in-house coding model: MAI-Code-1-Flash is now rolling out to all GitHub Copilot tiers (Free, Student, Pro, Pro+, Max) in VS Code.
- Beats Claude Haiku 4.5 by 16 points on SWE-Bench Pro (51.2% vs 35.2%) while using up to 60% fewer tokens on complex tasks.
- Trained inside the Copilot harness: unlike other models, it learned to operate within GitHub Copilot's actual production tool loop, not just coding benchmarks.
- Priced at $0.75 input / $4.50 output per million tokens, dramatically cheaper than frontier models; also available on Fireworks AI, Baseten, and OpenRouter.
- Adaptive solution length control: the model dynamically scales reasoning budget to task complexity, staying concise for simple requests and spending more on hard ones.
- Limitations: scores ~51% on SWE-Bench Pro (below Kimi K2.6 and Claude Opus); adversarial Einstellung traps remain below 50% accuracy -- not a frontier reasoner.
Microsoft just shipped its first homegrown coding model, and it's already live in your GitHub Copilot. MAI-Code-1-Flash is a lean, agentic model purpose-built for the everyday coding work that fills most of a developer's day. The headline claim: it beats Claude Haiku 4.5 by 16 percentage points on SWE-Bench Pro while using up to 60% fewer tokens to do it.
This is a bigger deal than it might first appear. For three years, Microsoft's AI product surface -- GitHub Copilot, Azure AI, Bing Chat, Microsoft 365 Copilot -- ran almost entirely on OpenAI models. MAI-Code-1-Flash is the first sign of a serious internal model strategy, and it's shipping directly to users, not just as a research preview.
Built for the editor, not the leaderboard
The core design bet here is unusual. Coding models are most useful when they perform well in the same environment developers use every day -- that's why Microsoft built MAI-Code-1-Flash with production workflows at the center, rather than optimizing only for benchmarks.
The most important design decision behind MAI-Code-1-Flash is that Microsoft trained it directly against the GitHub Copilot harness used in production, rather than optimizing only for offline benchmarks. That means the model learned to interact with the surrounding tools and systems that agentic coding actually requires: invoking commands, reading repository context, and working through multi-step tasks the way Copilot orchestrates them.
The practical consequence of this is subtle but important. The payoff of aligning training, evaluation, and production is that offline gains translate into real-world developer quality instead of evaporating when the model hits a real codebase. Most models are trained on coding tasks, then dropped into an agent loop they've never seen. MAI-Code-1-Flash learned the loop itself.
How it was built
The development pipeline spans pretraining, midtraining, supervised fine-tuning, and reinforcement learning, starting from MAI-Thinking-1's mid-training checkpoint. A lightweight supervised fine-tuning stage on curated instruction-following and agentic task data was applied on top of that checkpoint to establish reliable instruction- and format-following behavior. An additional "mid2" training phase used approximately 2 million diverse synthetic agentic tasks, organized into two progressive stages from simpler to more complex scenarios.
Microsoft trained it from the ground up on clean, traceable, and enterprise-grade data, without distillation from third-party models. That last part matters for enterprise customers worried about IP provenance -- a concern that has followed models like DeepSeek R1.
One of the key techniques is what Microsoft calls adaptive solution length control -- the model dynamically adjusts how much reasoning it spends based on task complexity:
- A simple variable rename uses minimal compute; a multi-file refactor gets more.
- Microsoft reports the model solving harder problems with up to 60% fewer tokens. That efficiency compounds in three ways: lower latency, lower cost, and smoother interactive workflows.
- If a model solves the same task in 60% fewer output tokens, you pay for roughly 40% of the output you would otherwise. Across thousands of daily requests per developer, that is a large, recurring saving.
What the benchmarks actually say
The numbers are strong, but worth reading carefully. Against Claude Haiku 4.5 -- the natural comparison point in the same lightweight tier -- MAI-Code-1-Flash wins across the board:
| Benchmark | MAI-Code-1-Flash | Claude Haiku 4.5 |
|---|---|---|
| SWE-Bench Pro | 51.2% | 35.2% |
| IF Bench (instruction following) | +28.9 pts lead | Baseline |
| Advanced IF (rubric-based) | +14.5 pts lead | Baseline |
| Adversarial reasoning benchmark | 85.8% | Lower |
The 85.8% figure is on an internal Microsoft benchmark that has not been independently reproduced. The SWE-Bench Pro 51% is more comparable -- it puts MAI-Code-1-Flash in the same tier as GPT-5.3, but below Kimi K2.6 (~58.6%), GLM-5.1 (~58.4%), and Claude Opus 4.6's baseline performance.
Microsoft also built a custom adversarial benchmark specifically designed to catch models that are pattern-matching rather than reasoning. Standard benchmarks reward memorization as much as reasoning -- a model that has seen the Monty Hall problem will answer it correctly, but invert the prizes and it fails. They built a 186-question, 34-category benchmark around adversarial traps like inverted classics, impossible tasks, and underdetermined scenarios. There is still room for the model to grow, since core adversarial categories like Einstellung traps remained below 50% accuracy. Einstellung traps are problems where a familiar solution pattern blocks you from finding a simpler one -- a known failure mode for smaller models.
Where it fits in your stack
MAI-Code-1-Flash is not claiming the top of the leaderboard -- it is positioned as an efficient everyday-coding model, not a frontier reasoner. Think of it as the workhorse you leave running all day, not the heavy hitter you call in for architecture decisions.
The tasks it's built for:
- Inline edits and refactors where speed matters more than deep reasoning
- Repository question answering and quick explanations of unfamiliar code
- Routine agentic tasks inside Copilot: running tests, applying small multi-file changes, fixing build errors
- High-volume coding assistance where token efficiency keeps costs manageable at scale
For hard reasoning tasks -- deep architectural work, gnarly multi-system debugging -- you'll still want to reach for a heavier model. MAI-Thinking-1 is Microsoft's first reasoning model, announced alongside Flash and currently in private preview on Microsoft Foundry. It is a mid-sized model with about 35 billion active parameters and a 128K context window, built for multi-step instructions, long-context reasoning, and code generation at low token cost.
Pricing and availability
MAI-Code-1-Flash is rolling out to Copilot Free, Student, Pro, Pro+, and Max plans. It is now rolling out to VS Code GitHub Copilot individual users. No additional setup is required. As the rollout progresses, you may see GitHub Copilot route tasks to MAI-Code-1-Flash through the Auto picker, or see the model available directly in the model picker.
At $0.75 input / $4.50 output per million tokens, MAI-Code-1-Flash is dramatically cheaper than frontier models like Claude Opus 4.8 ($5 / $25) or premium GPT tiers. MAI-Code-1-Flash is also available via Fireworks AI, Baseten, and OpenRouter for teams that want to use it outside of the Copilot interface.
The bigger picture
Microsoft has spent two years watching Cursor and Claude Code absorb the developer mindshare that GitHub Copilot should have owned by default. Copilot invented the AI pair-programmer category in 2021, had the VS Code integration, had GitHub's codebase signal -- and still lost early-adopter developers to whoever had the best model that week.
Microsoft's broader strategy is to give Copilot a model bench it owns end-to-end, reducing latency and unit cost for Copilot's hundreds of millions of users and lowering its reliance on external frontier labs. MAI-Code-1-Flash is the first piece of that stack to ship publicly. Designed and tuned specifically for GitHub Copilot, this marks the first in a new wave of purpose-built coding models from Microsoft. The implication is clear: more are coming.
The assumption worth updating: you no longer need a frontier model for most coding tasks. A small, purpose-built model trained on the actual tool environment can outperform larger general-purpose models on the work that actually matters -- and do it for a fraction of the cost. That's the bet MAI-Code-1-Flash is making, and the early numbers suggest it's paying off.