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 adds enterprise controls for Copilot agent commands, files, and network access
GitHub released enterprise-managed permissions for Copilot agent operations on September 9. Administrators can centrally set shell commands, file reads and writes, and access to network domains to blocked, approval required, or allowed without a prompt. User preferences, workspace settings, automatic approval, and earlier approvals cannot make the enterprise policy less restrictive. GitHub says the controls are generally available in the Copilot app, Copilot CLI, and Visual Studio Code sessions that use Agent Host for Copilot Business and Enterprise customers. Security and platform teams should begin with a minimum-permission baseline, test representative repositories, and expand only the operations that have a clear owner, audit trail, and rollback path.
AWS connects AgentCore evaluations to GitHub Actions for pre-merge agent regression gates
AWS published a reference workflow on September 8 for integrating Amazon Bedrock AgentCore Evaluations with GitHub Actions. The pipeline deploys a development agent and an OAuth-protected MCP server, invokes representative prompts, collects OpenTelemetry traces, and scores behavior before allowing a pull request to proceed. AWS describes built-in dimensions such as helpfulness, correctness, goal success, tool selection, tool parameters, and trajectory order, with custom and code-based evaluators available. The post compares three authentication patterns: evaluating stored traces, using a pre-authorized test user, or issuing machine-to-machine credentials for CI. Its implementation uses the third pattern. Teams should validate that CI credentials cannot escape their intended environment, that evaluation samples cover important failures, and that score variance, latency, evaluator cost, and rollback behavior are visible before treating the threshold as a release gate.
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: configuring team agent behavior in Copilot and validating results with a small task. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
GitHub Makes Global Model Policy Generally Available for Copilot
GitHub Makes Global Model Policy Generally Available for Copilot. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: standardizing Copilot model access rules across a team while preserving evidence of policy changes. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
GitHub Code Quality Adds Audit-Log Tracking for Enablement Changes
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Code Quality Adds Audit-Log Tracking for Enablement Changes.
GitHub Copilot Enters Slack Public Preview for Shared Coding Work
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Copilot Enters Slack Public Preview for Shared Coding Work.
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.
