Introducing the Microsoft Copilot harness: Unlocking the potential of truly multi-model agentic work (4 minute read)

# Introducing the Microsoft Copilot harness: Unlocking the potential of truly multi-model agentic work - The Official Microsoft Blog Source: [https://blogs.microsoft.com/blog/2026/10/28/introducing-the-microsoft-copilot-harness-unlocking-the-potential-of-truly-multi-model-agentic-work/](https://blogs.microsoft.com/blog/2026/10/28/introducing-the-microsoft-copilot-harness-unlocking-the-potential-of-truly-multi-model-agentic-work/) If you want to compete, you need to be multi\-model\. And if you want to take advantage of everything that different AI models have to offer, you need a great harness\. But building one that works seamlessly across multiple models and surfaces is incredibly hard\. You need to solve for performance, quality, and cost\. And then you have to maintain it, which is even harder\. Luckily, the GitHub engineering team built[a best\-in\-class, truly multi\-model harness](https://benchmarks.github.com/), which we’ve adopted company\-wide\. The Microsoft Copilot harness powers Copilot Code, Copilot Studio, the GitHub Copilot app, the CLI, VS Code, and more\. And today, we’re making that harness available through[Microsoft Foundry](https://devblogs.microsoft.com/foundry/microsoft-copilot-harness-in-foundry)\. That gives developers and enterprise customers a fully managed way to build agents that reason, use tools, and complete complex, long\-running tasks\. You get the right model for the job without switching the harness or the rest of your tech stack\. That frees up your time, energy, and resources to focus on your bottom line\. ### **What’s a harness, and why is it hard?** If the model supplies the intelligence, the harness is everything around the model\. It’s the orchestration layer that gives an agent the right instructions, context, execution environment, and controls to accomplish meaningful work\. And a harness worth its salt has support for open standards like MCP and agent skills, as well as agent plugins\. This is a fast\-moving space\. A frontier model today might fall behind tomorrow\. And building your own harness or model router to keep up can be painful and slow\. Now, you can build on the same harness Microsoft and GitHub ship in our own products, and you don’t have to maintain it\. We invest in science and engineering work to continually improve and evolve the harness and ensure high\-quality, efficient, and low\-cost performance across a range of models and workloads\. The benefits compound for us and our customers who use the harness to build and run their own agents\. Improve the harness, and every surface it touches benefits\. ### **Born in GitHub, battle\-tested at enterprise scale** The Copilot harness was built by the same GitHub engineers behind new technologies like our[multi\-model orchestration](https://github.blog/ai-and-ml/github-copilot/project-hydrafusion-frontier-quality-via-multi-model-orchestration/)\. And those technologies are only possible because we built our own harness\. Designed to be fast, token\-efficient, and predictable, it was our original, high\-quality harness\. And it had the highest satisfaction among our most demanding audience: developers\. That’s why we’re standardizing all of our Copilot experiences on the strongest foundation possible\. The harness is built to[perform across model families](https://x.com/ArtificialAnlys/status/2115477376981508419), with 20\+ frontier models plus bring your own key, so you can use the right model for the right job\. Instead of doing the work to keep up with and eval new models, lean on us to intelligently route work to the right model or models based on the task\. Our harness is flexible and configurable to any type of app, agent, or service\. We recently[ported the harness runtime to Rust](https://github.blog/ai-and-ml/generative-ai/migrating-the-github-copilot-runtime-to-rust-using-copilot/), which has resulted in industry\-leading performance and reductions in both session overhead and time\-to\-first token\. And because the Copilot harness powers surfaces across Microsoft, it’s battle\-tested and proven performant at the scale of millions of users and hundreds of real\-world use cases\. A unified harness lets us ship faster, learn faster, and improve Copilot over time\. And because the agents you build in Foundry can run on the same harness we’ve adopted across Microsoft, our continuous harness improvements will benefit your agents, too\. ### **Try it yourself** The[SDK is available to download](https://github.com/github/copilot-sdk), or you can run the harness in the cloud, all managed by Foundry\. Our platforms remain open and interoperable, so you can continue to bring in any harness and framework you want, too\. With the Copilot harness, Microsoft runs the agent loop and sandbox, with governance and optimization built in from day one\. You bring the instructions, skills, tools, and model choice\. This is an important step towards our vision of a stronger system around the model that preserves choice\. It represents the best of GitHub, brought to the Microsoft platform and beyond\. We’ll keep pushing the harness forward, so you can focus on what only you can build\. Tags:[GitHub](https://blogs.microsoft.com/blog/tag/github/),[GitHub Copilot](https://blogs.microsoft.com/blog/tag/github-copilot/),[Microsoft Copilot](https://blogs.microsoft.com/blog/tag/microsoft-copilot/),[Microsoft Foundry](https://blogs.microsoft.com/blog/tag/microsoft-foundry/)