
by Microsoft
Microsoft's cost-optimized coding model in the MAI-Code line, built for everyday GitHub Copilot workflows rather than frontier-scale reasoning.
Released August 11, 2026, MAI-Code-1.1-Flash is Microsoft's low-cost coding workhorse inside GitHub Copilot, tuned for everyday agentic work rather than frontier reasoning. Microsoft says it beats its June predecessor by 22% on Terminal-Bench 2.1, and since October 7, 2026 a 53GB quantized build can run on high-memory PCs.
| Job | Input | Output | Total |
|---|---|---|---|
| Summarise a 20-page PDF | $0.0060 | $0.0012 | $0.0072 |
| Support reply | $0.0004 | $0.0004 | $0.0008 |
| One coding agent run | $0.040 | $0.024 | $0.064 |
Budgets: 20-page PDF = 30k in / 1k out · Support reply = 2k in / 300 out · Coding agent run = 200k in / 20k out. Computed from the vendor's per-token prices at render time; cached-input discounts are not applied.
Through GitHub Copilot and Microsoft Foundry, input runs $0.20 per 1M tokens, cached input $0.02 per 1M, and output $1.20 per 1M, the same figures as Azure's global-standard retail meters on October 14, 2026, a 73.3% cut across the board versus MAI-Code-1-Flash's $0.75/$0.075/$4.50 rates. Annual Copilot Pro and Pro+ subscribers still on legacy premium-request billing pay a 0.25x premium request multiplier. Calls to the on-device build carry no per-inference charge, per Microsoft.
MAI-Code-1.1-Flash is Microsoft's small-tier coding model for GitHub Copilot, built as a sparse Mixture-of-Experts design with 138B total parameters per its model card. It reads screenshots and UI mockups natively, and a 256,000-token context window lets it take in a mid-size repository in one pass.
Reads
Writes
Native Vision Input
New in 1.1: the model reads UI mockups, diagrams, and error screenshots on its own, something the June text-only release couldn't do.
256K Context Window
Holds an entire mid-size repository or a long multi-file diff in context, with a 128K token output ceiling for long generated diffs or docs.
Agentic Terminal Coding
Tuned against Copilot CLI's own reinforcement-learning environments, where it posts its strongest score on the terminal-coding benchmark.
Prompt Caching
Cached input tokens cost a small fraction of the standard input rate, a real discount for repeat-context agent loops. Exact rates are in the pricing FAQ.
Native Function Calling
Built-in tool use and structured output support that plugs directly into Copilot's agent loop without a separate function-calling adapter.
On-Device Option
A quantized build announced October 7, 2026 shrinks the model by 80% for high-memory PCs, and Microsoft charges nothing per local call.
SWE-bench Verified, the headline coding benchmark for this release
Source: Microsoft MAI-Code-1.1-Flash model cardCheaper than 75% of the 103 GA models with a published price, and mid-pack on SWE-bench Verified (rank 24 of 39).
| Measure | This model | Rank | Median |
|---|---|---|---|
| Blended price (3:1)$ per 1M tokens | $0.45/M | #27 / 103 | peer median $1.71/M |
| SWE-bench Verified% solved | 72.6% | #24 / 39 | peer median 76.5% |
Ranks are against GA models on Hokai that publish the same figure; ties share a rank.
A benchmark is an exam, not the job. Scores transfer unevenly between tasks, so weigh the one closest to your workload and read every figure with its source.
| Model | Lab | Context | In / out per 1M | Reads and writes |
|---|---|---|---|---|
| Microsoft | 256K | $0.20 / $1.20 | text, image → text, code | |
| DeepSeek | 1M | $0.15 / $0.60 | text → text | |
| Moonshot AI | 262K | $0.95 / $4 | text, image, video, code → text, code | |
| OpenAI | 200K | $1 / $6 | text, image → text, code |
Training data
Pre-training data is filtered to demote harmful content before base-model learning; supervised fine-tuning and reinforcement learning stages then reinforce safe, helpful behavior, per Microsoft's published model card. Microsoft discloses a pretraining cutoff of December 2025 for this 1.1 refresh.
| Name | Endpoint | Auth |
|---|---|---|
| GitHub Copilot | https://github.blog/changelog/2026-08-11-mai-code-1-1-flash-available-in-github-copilot/ | GitHub Copilot subscription (Free through Enterprise) |
| Microsoft Foundry | https://microsoft.ai/models/mai-code-1-flash/ | Azure AI Foundry API key |
Attach a screenshot or mockup instead of describing UI in words
Paste a screenshot of the broken layout alongside 'Fix this component to match this design.'
Native vision input is new in 1.1, so image context resolves UI ambiguity a text-only prompt leaves to guesswork.
Let the CLI agent loop run rather than single-shot prompting
Use Copilot CLI's agent mode for multi-file terminal tasks instead of one large prompt.
The model was tuned against Copilot CLI's own reinforcement-learning environments and scores highest in that agentic loop.
Off by default for Business/Enterprise
Business and Enterprise Copilot tenants do not get MAI-Code-1.1-Flash automatically; it stays hidden until an administrator turns the policy on in Copilot settings.
Workaround: Have a Copilot admin enable the MAI-Code-1.1-Flash policy in the organization's settings before asking developers to select it.
Free and Student tiers can't pick it manually
Copilot Free and Student users only get MAI-Code-1.1-Flash through automatic model selection; there is no manual model picker on those plans.
Workaround: Upgrade to Copilot Pro or above to select MAI-Code-1.1-Flash directly, or trust auto-select to route eligible requests to it.
No standalone reasoning mode
The model handles single-pass coding well but has no extended-thinking toggle, so very deliberate multi-step problems can undershoot what a dedicated reasoning model would produce.
Workaround: Route reasoning-heavy planning to MAI-Thinking-1 or a frontier reasoning model, then hand the concrete coding steps to MAI-Code-1.1-Flash.
Thin distribution outside Copilot
First-party access runs through Microsoft Foundry and GitHub Copilot; OpenRouter listed no MAI model on October 14, 2026, and there is no confirmed AWS Bedrock or Google Vertex listing.
Workaround: Plan for a Foundry or Copilot integration path rather than assuming multi-cloud availability when architecting a deployment.
Local build needs a 120GB-class machine
The October 2026 on-device build is a 53GB quantization at about 3.3 bits per weight that peaked at 75.5GB of memory at 256K context in Microsoft's tests, and Microsoft recommends more than 120GB of RAM.
Workaround: Leave Copilot on Auto so smaller machines route work to the cloud model, and keep sessions shorter on local runs because the key-value cache grows with context.
MAI-Code-1.1-Flash local build · 07 Oct 2026
Quantized on-device build (about 3.3 bits per weight, 53GB) announced; experimental GitHub Copilot access by end of October 2026.
MAI-Code-1.1-Flash · 11 Aug 2026
Adds native vision input, 72.6% SWE-bench Verified, 62.9% Terminal-Bench 2.1, and a steep price cut versus the predecessor.
MAI-Code-1-Flash · 02 Jun 2026
Initial release, text-only. 71.6% SWE-bench Verified, 54.8% Terminal-Bench 2. Retired across GitHub Copilot on 2026-09-10.
MAI-Code-1.1-Flash costs $0.20 per 1M input tokens, $0.02 per 1M cached input tokens, and $1.20 per 1M output tokens through Microsoft Foundry and GitHub Copilot, matching Azure's retail price list on October 14, 2026. That is a 73.3% cut across all three rates versus MAI-Code-1-Flash's $0.75/$0.075/$4.50. Annual Copilot subscribers on legacy premium-request billing pay a 0.25x multiplier, and Microsoft charges nothing for local calls.
On the terminal-coding benchmark, DeepSeek-V4-Flash-0731 posts a stronger 82.7% pass rate at a lower blended token price than Microsoft's model manages on that same eval, per comparisons published after both launched. Microsoft has not published a head-to-head SWE-bench Verified score for DeepSeek's model, so that axis remains a Microsoft-only claim; DeepSeek is the better raw-benchmark pick for teams not tied to GitHub Copilot.
Proprietary. Microsoft has not published MAI-Code-1.1-Flash weights on Hugging Face or under any open license (Hokai checked October 14, 2026), even though a quantized local build announced on October 7, 2026 runs on PCs with 120GB or more of RAM through GitHub Copilot's Windows ML provider. Cloud access runs through GitHub Copilot, from the Free plan through Enterprise, and Microsoft Foundry.
Microsoft has not published a specific data-retention or training-on-inputs policy for this release. Its model card outlines pre-training content filters plus a fine-tuning and reinforcement-learning stage aimed at safe, helpful behavior, but does not state whether Copilot request data feeds back into future training runs.
Engineering teams already standing on GitHub Copilot, chasing a cheap, quick model for CLI- or .NET-heavy agent work, get the most from it, and owners of 128GB-class workstations can now keep eligible tasks on-device. Teams needing deliberate multi-step reasoning should look at MAI-Thinking-1 instead, and teams chasing the strongest raw terminal score at a similar price should compare DeepSeek-V4-Flash-0731 before committing.
MAI-Code-1.1-Flash is Microsoft's in-house small-tier coding model, released August 11, 2026 as the successor to MAI-Code-1-Flash (released June 2, 2026). Its August model card lists a sparse Mixture-of-Experts architecture with 138B total parameters and 5B active per token, while Microsoft's October 7, 2026 post on the local build describes the same model as 137B total and 6.8B active. It sits inside Microsoft's MAI model family alongside MAI-Thinking-1, which handles the deliberate reasoning work this model does not attempt, and it exists specifically to be GitHub Copilot's low-cost, high-volume coding workhorse rather than a general frontier model.
On benchmarks, MAI-Code-1.1-Flash scores 72.6% on SWE-bench Verified, averaging 8.6K tokens per solved task, and 62.9% on Terminal-Bench 2.1 inside GitHub Copilot CLI, averaging 17.0K tokens, per Microsoft's model card. In that card's own runs the June MAI-Code-1-Flash managed 71.6% and 51.7%, Claude Haiku 4.5 69.8% and 49.4%, and GPT-5.4 mini 69.2% and 60.7%, so the terminal result is the real step forward and the SWE-bench lead over those peers is a point or three. Microsoft also reports a 15% gain on .NET-specific tasks and roughly 25% fewer tokens per completed task than the June release. For image-to-code work, the card records 74.1% on Text2WebApp and 42.1% on ScreenShot2WebApp, both internal Microsoft tests.
Context window sits at 256,000 tokens with a 128,000-token maximum output ceiling, unchanged from the predecessor. Microsoft reports 25% faster token streaming inside GitHub Copilot's CLI, which combined with the lower token count per solve shortens the wall-clock time of longer agentic sessions. Teams comparing agentic coding tools more broadly, including terminal-native options, can see how it stacks up in Hokai's Cursor Composer vs. Claude Code comparison and its locally runnable coding models roundup.
Running it on your own machine became an option on October 7, 2026. Microsoft's Windows Command Line team describes a quantized build at roughly 3.3 bits per weight that takes 53GB, 80% smaller than the cloud version, and peaked at 75.5GB of memory at the full 256K context on a Surface Laptop Ultra with NVIDIA RTX Spark. In Microsoft's October 5 tests that local build scored 70.8% on SWE-bench Verified and 66.3% on Terminal-Bench 2.1, against 32.0% and 23.6% for OpenAI's larger gpt-oss open-weight model on the same harness. Microsoft charges nothing per local call and says experimental access reaches the GitHub Copilot app, Copilot CLI and VS Code by the end of October 2026, through Copilot's Auto routing or by choosing it under the Windows ML provider. Developers used to pulling open-weight coders into Ollama or LM Studio should note the difference: Microsoft has published no Hugging Face repository or open-weight license for this model, so GitHub Copilot is the supported local path.
Inputs are text and, new in this release, native images: MAI-Code-1.1-Flash can read screenshots, diagrams, and UI mockups directly, a capability the text-only June release lacked. Output stays text and code, with native function calling for tool use. There is no toggleable extended-reasoning mode; Microsoft routes deliberate multi-step planning to the separate MAI-Thinking-1 model, keeping this one tuned for single-pass code generation, repository question answering, and refactoring.
Pricing dropped sharply from the June release: Microsoft cut the rate across every tier of the per-token structure, framing the update as delivering more capability for meaningfully less spend. The model bills through GitHub Copilot and through Microsoft Foundry directly. Exact current rates and worked cost examples live in the pricing FAQ below.
MAI-Code-1.1-Flash is live across VS Code, Visual Studio, JetBrains IDEs, Eclipse, Xcode, GitHub Mobile, Copilot CLI, the Copilot cloud agent, and Copilot Chat on GitHub, spanning every Copilot plan from Free through Enterprise, see what Microsoft Copilot actually gets you across its different products. Free and Student users get it only through automatic model selection; paid tiers can select it manually. Business and Enterprise administrators have to switch on its Copilot policy themselves, since it ships off by default at the organization level. Outside Copilot it is reachable through Microsoft Foundry on Azure; OpenRouter's catalog listed no MAI model when Hokai checked in mid-October 2026, and no AWS Bedrock or Google Vertex listing has surfaced.
On safety, Microsoft's published model card describes filtering harmful content out of the pre-training mixture, then applying supervised fine-tuning and reinforcement learning to shape model behavior toward safe, helpful output. Weights are not open, local build included, and Microsoft discloses a pretraining data cutoff of December 2025 for this 1.1 refresh.
The model fits teams already running on GitHub Copilot who want an inexpensive, fast agent for CLI-heavy or .NET-heavy work, and for high-volume tasks like bulk refactors or repo Q&A where a frontier-priced model is overkill; Hokai's best AI coding assistants roundup and free coding-question tools guide cover the wider field for teams still choosing. Teams that need deliberate, multi-step reasoning are better served by MAI-Thinking-1 or a frontier coding model, and DeepSeek-V4-Flash-0731, from DeepSeek, posts a stronger terminal-benchmark score at a lower blended price for teams not tied to the Copilot ecosystem, while Kimi K2.7-Code, its lower-latency Kimi K2.7 Code HighSpeed variant, and Google's Gemini 3.5 Flash are the closest open-weight, speed-tier, and budget-tier alternatives respectively; GPT-5.6 Luna is the closest OpenAI-ecosystem pick, and Hokai's guide to choosing an AI assistant covers the wider field, browsable in full in the models directory. MAI-Code-1-Flash, the June predecessor, was retired across all GitHub Copilot surfaces on September 10, 2026, and Microsoft has described 1.1 as a drop-in replacement at the prompt level rather than a rewrite.
Specifications on this page (context window, token prices, benchmark scores, licence) are read from Microsoft's own model card and documentation. The verdict is Hokai's reading of them, not the provider's claim.