MAI-Code-1.1-Flash Arrives in GitHub Copilot as the Previous Model Heads for September Retirement
The new model adds vision and a lower list price, while plan access, enterprise policy, and a September 10 migration deadline shape the real user task.
Key takeaways
GitHub announced on August 11, 2026 that Microsoft's MAI-Code-1.1-Flash is rolling out in Copilot, while MAI-Code-1-Flash will be deprecated across Copilot experiences on September 10. The new small-tier coding model adds native image understanding and improvements in coding quality, instruction following, tool use, and performance. GitHub says its list price is 73 percent lower than the prior model and shows a 0.25x premium-request multiplier for annual Copilot subscribers. Free and Student users receive it through automatic model selection; major paid plans can select it manually, and Business or Enterprise administrators must enable a policy that is off by default. Compare both models on the same task, including quality, latency, tools, and AI Credits, before changing defaults.
# MAI-Code-1.1-Flash Arrives in GitHub Copilot as the Previous Model Heads for September Retirement
August 13, 2026
Direct answer
Treat the new release and old-model retirement as one migration. Confirm plan and policy access, compare both models on a fixed task, then replace pinned configurations before September 10.
Fact sources
GitHub announced the MAI-Code-1.1-Flash rollout on August 11, 2026, with native vision and coding improvements.
GitHub states a 73 percent lower list price than MAI-Code-1-Flash and a 0.25x premium-request multiplier for annual Copilot subscribers.
MAI-Code-1-Flash is scheduled for deprecation across Copilot on September 10, 2026, with version 1.1 as the suggested replacement.
Five steps for the MAI-Code-1.1 migration
- Check the model picker, plan, regional availability, and enterprise model policy.
- Choose one fixed task covering code understanding, edits, tests, and optional image input.
- Record quality, time, failures, tool calls, and AI Credits for both model versions.
- Update pinned models, automations, and team documentation before September 10.
- Keep a fallback model and human review for visual decisions and production changes.
Why it matters
A model update changes capability, pricing, and availability together. A list-price percentage cannot predict the cost of different prompts, cache behavior, tools, retries, or plans.
Impact for ordinary AI users
Individuals may encounter the model through auto selection or choose it manually on paid plans. Enterprise users may not see it until an administrator enables the policy, and pinned workflows need a dated migration plan.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, and logs, then record the result in the team runbook.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Can every Copilot user select the model manually?
No. GitHub says Free and Student access comes through auto selection, while major paid plans can manually select it.
Does 73 percent lower mean every task costs 73 percent less?
No. It is a provider list-price comparison; actual cost depends on the plan, tokens, cache, tools, and retries.
Why is the model missing in an enterprise?
The Business and Enterprise model policy is off by default and must be enabled by an administrator.
Source links
- GitHub Changelog: MAI-Code-1.1-Flash available (2026-08-11)
- GitHub Changelog: MAI-Code-1-Flash deprecation (2026-08-11)
- GitHub Docs: Models and pricing for Copilot
- Microsoft AI: MAI-Code-1.1-Flash
What this means for everyday users
Record plan, region, policy, test task, image input, tool calls, AI Credits, fallback model, and migration date.
Related reading
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review
GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.
Copilot in Visual Studio Adds PR Exploration, a BYOM Migration, and NuGet Fixes
GitHub summarized three September updates for Copilot in Visual Studio 2026 on October 22, 2026. The Git agent can explore an attached pull request and link back to comments and files. Bring Your Own Model remains in preview but now requires the new Agent experience, and previously configured Ollama models must be added again. NuGet Audit warnings can open Copilot Chat with the NuGet MCP server to propose dependency fixes. This article gives .NET developers a cautious upgrade checklist: preserve current settings, validate each feature independently, review package and lock-file changes, run targeted tests and vulnerability scans, and keep a rollback path. Summaries and suggested fixes remain review inputs, not verified outcomes.
GitHub Copilot Usage API Names Custom Skills, Agents, and MCP Servers: How to Read the Report
GitHub updated the Copilot usage metrics API on October 22, 2026, so customer-defined skills, agents, MCP servers, slash commands, and plugins can appear by configured name instead of being grouped entirely under other or custom. Each totals_by_* list now includes as many as 25 entries per record, up from five. This article helps administrators turn the change into a reliable adoption report. It covers required Copilot CLI and SDK versions, a naming review before reports are shared, one-day and 28-day comparisons, and a reconciliation check against known pilots. It also explains why historical days, path-like names, outdated clients, and blocked telemetry can still undercount activity. The metrics are useful for trends and enablement, not exact billing.
GitHub Copilot Global Defaults Take Effect: Review Unconfigured Features Before October 26
GitHub began enforcing the global default policy for Copilot Business and Copilot Enterprise on October 22, 2026, with the gradual rollout continuing through October 26. Eligible generally available features that remain Unconfigured will receive the selected default: Enabled, Disabled, or Let organizations decide. This is a one-time change. Explicit feature choices are preserved, and preview features remain opt-in. This article gives administrators a practical review before the policy reaches their enterprise or organization. It separates unconfigured items from deliberate decisions, checks both Features and clients and MCP servers in Copilot, records exceptions, and defines a user-access verification. The goal is to prevent silent access changes caused by assuming that Unconfigured means disabled.
GitHub Copilot Impact Dashboard Adds Industry Comparisons: How to Read the Median and Top Decile
GitHub added an Industry comparison section to the Copilot impact dashboard on October 22, 2026. Eligible enterprises and standalone organizations can opt in to compare agent-first or multi-agent adoption and pull-request merge-rate leverage with aggregated participating peers. When enough peers participate, scores are placed against a 28-day median and, as the group grows, a top-decile reference. This article explains how to decide whether to opt in and how to avoid overreading the result. It covers company-size and industry groups, fallback to broader peer groups when samples are small, regional separation for data-residency customers, daily refreshes, and 30-day deletion of aggregated benchmarks. The comparison is context for planning, not a complete industry census or employee ranking.
Summary
MAI-Code-1.1-Flash is a capability and pricing migration with a dated retirement. Use a controlled task and real billing evidence before switching defaults.
