Microsoft 通过 Foundry 开放 Copilot harness,支持多模型 Agent 开发
Core highlights
Microsoft announced on its official blog that it will open Copilot Harness through Microsoft Foundry—a multi-model orchestration layer built by the GitHub engineering team and used across Microsoft's product line for years.
What happened
Put simply, the model handles "being smart," and the harness handles "everything around the model": instructions, context, execution environment, and control. Microsoft turns this in-house harness into a managed service, so developers get a unified agent runtime across models and surfaces without building their own.
What happened (continued)
Copilot Harness backs every surface—Copilot Code, Copilot Studio, the GitHub Copilot app, CLI, VS Code. It supports open standards like MCP, agent skills, and agent plugins, and can intelligently route across 20+ frontier models by task, also supporting bring-your-own-key (BYOK). The runtime recently migrated to Rust, cutting session overhead and first-token latency.
Technical details
Microsoft stresses "models expire, harness doesn't": a frontier model leads today and may lag tomorrow, but the orchestration layer evolves continuously. Improve the harness and every surface it touches benefits. Agents on Foundry run on the same harness, so Microsoft's ongoing optimization also feeds users' agents.
How it compares
Unlike Anthropic's model-client closed loop, Microsoft makes the orchestration layer a callable managed service—more of a "platform" play. The SDK is open-sourced (github/copilot-sdk), runnable locally or in cloud, preserving flexibility to bring your own framework.
Industry impact
For enterprises, this means using the right model for the right job without switching the whole stack. For developers, a managed harness lowers the bar to build production-grade agents and bakes governance and optimization in from day one.
Practical notes
If you already use Copilot surfaces, the harness is the common substrate—optimizing once helps everywhere. BYOK keeps your model spend portable.
What to watch
The Rust migration and multi-model routing are the quiet differentiators; watch latency and cost as they stabilize.
Takeaway
Microsoft's move is "harness as a service." In a world where models churn monthly, owning the durable orchestration layer may matter more than owning any single model.
Why this matters now
In a world where models churn monthly, the durable asset may be the orchestration layer, not any single model. Microsoft turning its internal harness into a managed service is a statement that the platform—not the model—is the long-term moat.
Practical guidance for readers
If you already use Copilot surfaces, the harness is the common substrate; optimizing it once helps everywhere. Bring-your-own-key keeps your model spend portable and prevents lock-in to one provider's economics.
Risks and open questions
The Rust migration and multi-model routing are the quiet differentiators to watch. Their real value shows up only in latency and cost at scale, which take time and volume to validate.
Closing perspective
Microsoft's move reframes the competitive question from "which model is best" to "whose harness runs my agents best." That is a shrewder long-game than it looks: models depreciate monthly, but a managed orchestration layer with routing, governance, and optimization compounds in value as every surface above it benefits. Opening it through Foundry invites an ecosystem to build on top, deepening lock-in through utility rather than contract. The open-sourced SDK is the clever half-step—enough to earn developer trust, while the managed service remains the monetization core. For enterprises, the pragmatic read is to evaluate the harness, not just the model, because over a multi-year horizon the orchestration layer will shape total cost and capability far more than any single release.
The bottom line
Microsoft is playing the longer game: harness over model. Models depreciate monthly; a managed orchestration layer compounds. Opening it through Foundry invites an ecosystem to build on top, locking in through utility. Evaluate the harness, not just the model—over years, the orchestration layer will shape your total cost and capability far more than any single release.
A note on the platform logic
Microsoft's decision to open its internal harness is a classic platform move dressed in AI clothing: give developers a stable, capable substrate, and they will build on top of it, turning utility into lock-in that no contract alone could enforce. The open-sourced SDK is the trust-generating half-step—enough openness to earn developer goodwill, while the managed service remains the monetization core. For enterprises, the evaluation lens should widen from "which model" to "which harness," because over a multi-year horizon the orchestration layer—routing, governance, optimization—shapes total cost and capability far more than any single release. The strategic read is that Microsoft is betting the durable asset is the layer that survives model churn, and by externalizing it they invite an ecosystem to make that bet with them, compounding the advantage with every surface that adopts it.