Back Home

模型工程

Microsoft Specializes MAI-Code Through In-Product Reinforcement Learning, Extending the Same Checkpoint to an Excel Agent

Microsoft has unveiled a “hill-climbing” post-training process that feeds product tools, graders, and real-world usage signals back into model iteration. After further training in an Excel environment, MAI-Code-1-Flash can be served on older GPUs, but the company has not disclosed its parameter count, evaluation sets, or raw experimental data.

Steven C. Price · CC BY-SA 4.0 · Image source
zh-Hant

Microsoft disclosed on July 23 the results of in-product post-training for two MAI models. Its “hill-climbing machine” connects a base checkpoint, agent harness, tool execution environment, product evaluations, and updated weights in a loop, rather than relying solely on general-purpose benchmarks to select model versions. The team first deployed the small agentic model MAI-Code-1-Flash in GitHub Copilot, then used that checkpoint in an Excel reinforcement learning environment, where the model practiced selecting tools and performing spreadsheet operations while a grader updated its policy based on the outcomes.

Microsoft said MAI-Code-1-Flash achieved a code acceptance rate in VS Code approximately 10% higher than GPT-5.4 Mini and Claude Haiku 4.5, while using 10% fewer tokens at the median. Its cross-day return rate was 6% and 11% higher, respectively. Product feedback for the Excel variant on common tasks was described as comparable to GPT-5.6, and the model can be deployed on NVIDIA H100 or A100 GPUs without requiring the latest generation of accelerators. This suggests that the efficiency of agentic models depends not only on reducing parameter count, but also on post-training for a fixed toolset, state transitions, and success criteria.

The key technical advantage is that the product owner controls the model, harness, and grading signals together, enabling failed trajectories to be converted quickly into training data for the next iteration. The tradeoff is that the model may overfit to a specific interface; if tool versions or workflows change, its online advantage may not persist. Microsoft also did not disclose the model’s parameters, the distribution of Excel tasks, statistical intervals, or the GPT-5.6 comparison setup, while acceptance and return rates are not equivalent to code correctness. Engineering teams should next examine how offline evaluations and online metrics can prevent reward hacking, and whether product data can be safely fed back into training with appropriate privacy, licensing, and bias controls.

Sources

  1. Hill-Climbing MAI models for GitHub Copilot and Excel
  2. MAI-Code-1-Flash available on more Copilot surfaces
  3. Getting more from each token: How Copilot improves context handling and model routing