AI agents · OpenClaw · self-hosting · automation

Quick Answer

Kimi K3 vs MAI-Code-1.1-Flash in Copilot 2026

Published:

The Short Answer

GitHub is betting on model choice, not model loyalty. In one week of August 2026 Copilot gained two models with opposite jobs: Kimi K3 (August 6) for capable agentic work at open-weight pricing, and MAI-Code-1.1-Flash (August 11) for fast, cheap, image-aware everyday coding.

Kimi K3MAI-Code-1.1-FlashGPT-5.6 SolClaude Opus 5
In Copilot sinceAug 6, 2026Aug 11, 2026AvailableAvailable
Price /MTok$3 / $15Lowest tier$5 / $30$5 / $25
Cached input$0.30$0.50
PlansPro, Pro+, Max, Business, EnterpriseIncl. Free + Student (auto-select)PaidPaid
Image understanding✅ native
Open weights✅ (July 27, 2026)
Hosted byFireworks AIMicrosoftOpenAIAnthropic
Best forAgentic multi-step workVolume + visual inputHard reasoningLong-horizon refactors

Prices are provider list rates under Copilot usage-based billing, verified August 18, 2026.

Cost Per Real Task

Headline rates mislead. At a representative 30K input / 5K output coding task:

ModelCost per taskRelative
MAI-Code-1.1-Flashlowest tierbaseline
Kimi K3$0.165
Claude Sonnet 5$0.1100.67× K3
Claude Opus 5$0.2751.7× K3
GPT-5.6 Sol$0.3001.8× K3

Note what that reveals: Kimi K3 is not the cheapest capable option in Copilot. Claude Sonnet 5 at $2/$10 undercuts it by a third on the same task shape. K3’s argument is agentic reliability and the fact that its weights are public, not raw price.

Where Each One Wins

Kimi K3 — agentic work you don’t want to babysit

K3’s open weights landed July 27, 2026, and it has since become a default reference point for multi-step agent workloads: consistent tool-calling, stable behaviour across long sessions, and pricing that doesn’t punish a 40-step run. Inside Copilot it’s available in VS Code, Visual Studio, Copilot CLI and on github.com.

The $0.30 cached input rate matters more than it looks. Agentic loops re-send a large stable prefix — repo context, tool definitions, instructions — on every step. A 10× cache discount is what makes long runs affordable.

The catch: it is billed at provider list pricing under usage-based billing, so it consumes budget rather than sitting inside a flat allowance. Watch spend before turning it loose on a fleet.

MAI-Code-1.1-Flash — the one most people will actually use

Microsoft’s own model is the strategic move here. It reaches Free and Student users through auto model selection, meaning it becomes the default coding model for the largest slice of Copilot’s user base without anyone picking it.

The differentiator is native image understanding. Paste a screenshot of a broken layout, a design mock, an error dialog or a whiteboard sketch and it works from the image directly. Among the fast tiers that is genuinely uncommon, and it maps to how developers actually debug UI.

The August 11 release also claims improvements to coding quality, instruction following, tool use and performance over MAI-Code-1-Flash. Treat those as vendor-reported until independent benchmarks land.

Enterprise note: admins may need to enable the model by policy before their organisation sees it.

The frontier models — keep them for the hard 10%

Claude Opus 5 ($5/$25, 1M context, 128K max output) remains the pick for long-horizon refactors where the deliverable is a large coherent change rather than an answer. GPT-5.6 Sol ($5/$30) is the strongest general reasoner. Both cost roughly 2× Kimi K3 per task, which is correct pricing for decisions that are expensive to get wrong and terrible pricing for autocomplete.

The Routing Policy That Works

  1. Inline completion, small edits, anything with a screenshot → MAI-Code-1.1-Flash. Cheapest, fast, image-aware.
  2. Multi-step agent tasks, tool-heavy runs → Kimi K3. Cache discount does the heavy lifting.
  3. Cost-sensitive mid-tier work → Claude Sonnet 5 at $2/$10 — cheaper per task than K3 and permanently priced after Anthropic cancelled the September 2026 increase.
  4. Architecture, gnarly debugging, large refactors → Claude Opus 5 or GPT-5.6 Sol.
  5. Measure cost per completed task, not per token. A cheap model that needs three attempts is the expensive one.

What GitHub’s Strategy Signals

Adding a Chinese open-weight model and a Microsoft in-house model in the same week is not an accident. Copilot is positioning as a router, not a model — the value is the surface, the permissions, the enterprise controls and the IDE integration, with the model as a swappable component.

That’s the opposite of Cursor’s approach, which is vertically integrating everything from the model to code hosting. Model-choice platforms give you portability; vertically integrated ones give you speed. Both bets are live.

Last verified: August 18, 2026. Pricing from GitHub Copilot’s model pricing documentation.

Sources