Gate 1
Access
Record plan, account, Copilot surface, client version, rollout evidence, manual or automatic selection, explicit model state, delegated default, and exclusions.
September 10 cutover record
MAI-Code Copilot Migration Readiness
Describe your Copilot plan, clients, policies, old-model references, task suite and budget. Generate a migration checklist without assuming rollout or a universal cost multiplier.
Four migration gates
Gate 2
Inventory
Find 1.0 references in model pickers, instructions, runbooks, screenshots, policies, evaluation fixtures, reports, budgets, and training.
Gate 3
Evaluation
Run identical tasks for quality, instruction following, tools, tests, security, vision, total latency, retries, edits, and accepted work.
Gate 4
Cutover
Name the owner, pilot group, enablement date, fallback model, documentation change, budget alert, rollback window, and September 10 completion date.
Continue with source guides
Frequently Asked Questions
It creates an access, inventory, evaluation, and cutover checklist from the information you provide. It does not inspect GitHub settings, enable a policy, select a model, or modify repositories.
GitHub says it will deprecate MAI-Code-1-Flash across Copilot on September 10, 2026 and recommends MAI-Code-1.1-Flash.
There is no universal answer. An explicit model setting wins. If the GA model is unconfigured and delegates, it inherits the current default-availability policy; exclusions and enterprise, organization, plan, client, rollout, data-residency, and FedRAMP constraints still apply.
No. GitHub's launch states a 0.25x premium request multiplier for annual subscribers. Confirm the exact plan, allowance, and billing model.
The replacement is selectable on required clients, representative tasks meet quality and security gates, billing is understood, documentation is updated, and owners and fallback are named.