What Is Windows Agent Runtime? Microsoft Build 2026 Preview
What Is Windows Agent Runtime?
Windows Agent Runtime is Microsoft’s new OS-level platform for AI agents, reaching Windows Insiders in June 2026 and headlining Microsoft Build 2026 (June 2–3, Fort Mason Center, San Francisco). The bet: Windows becomes an orchestration layer for autonomous digital workers, not just a container for applications.
Last verified: May 31, 2026.
TL;DR
| Item | Detail |
|---|---|
| Announced at | Microsoft Build 2026 (June 2–3, 2026, Fort Mason SF) |
| Preview ships | June 2026 (Windows Insiders) |
| General availability | Not yet announced |
| Initial scope | Text agents on structured data (JSON, XML, PDF) |
| Deferred | Vision-based agents (screen-pixel understanding) |
| SDK | Microsoft Agent Framework (open-source, .NET + Python) |
| Sister products | Copilot agent mode, Windows Agent Store, Windows 365 for Agents, Azure AI Foundry |
| Model support | Claude, GPT-5.5, Gemini, local — pluggable |
The strategic claim
Satya Nadella’s Build 2026 keynote thesis: the operating system is no longer a container for applications — it’s an orchestration layer for autonomous digital workers. Windows Agent Runtime is the technical expression of that thesis.
The historical analogue Microsoft is leaning on: just as Win32 and COM made cross-app integration possible in the 1990s, the Windows Agent Runtime is meant to make cross-agent and cross-app agent invocation possible in the late 2020s. Apps publish agents; agents discover each other; the OS handles identity, policy, audit, and sandboxing.
What it actually does (June 2026 preview)
Three primary capabilities, all scoped narrowly for the first preview:
1. Agent registration and discovery
Apps register agents through standardized Windows APIs. Other apps — and the OS itself — can enumerate registered agents and invoke them through a consistent contract (name, capabilities schema, IO schema, auth model). This is the cross-app primitive: Outlook can invoke an Excel-published agent without bespoke integration code.
2. Structured-data input / output
The preview is explicitly text-only on structured data: JSON, XML, PDF. No screen pixels, no images, no audio. This is a deliberate scope limit — Microsoft wants to ship the platform plumbing without committing to a vision-agent security model yet. Vision-based agents (screen understanding, OCR, GUI automation) are on a later roadmap.
3. Sandboxed execution with enterprise policy
Agents run in sandboxes (more isolated than UWP apps, less than full VMs). Enterprise admins govern:
- Which agent providers are allowed (Microsoft, Anthropic, OpenAI, Google, third-party, local).
- What data agents can access (file system scopes, Microsoft Graph, line-of-business APIs).
- Audit logging — every agent invocation is logged to Microsoft Purview / Intune.
- Network policy — egress controls per agent.
This is the enterprise unlock — the platform is built for IT to govern, not just for developers to ship.
What you need to build for it
Microsoft Agent Framework
The SDK is Microsoft Agent Framework (open source, github.com/microsoft/agent-framework), shipping for both .NET and Python. It provides:
- Agent definition primitives (capabilities, IO schemas, tool registration).
- Multi-agent workflow orchestration (sequential, parallel, hierarchical).
- Model adapters (Azure OpenAI, Anthropic, Google Vertex, OpenAI direct, local via ONNX).
- Test harnesses and the Windows Agent Runtime emulator for local dev.
Model choice
Pluggable. Claude Opus 4.8, GPT-5.5, Gemini 3.5 Flash, and local models all work. Microsoft samples lean on Microsoft Foundry and Azure AI inference, but nothing in the runtime forces a model. Anthropic models are already integrated with Microsoft 365 Copilot (with admin-toggle defaults for Excel and PowerPoint, Word coming summer 2026) and that pattern extends to runtime-registered agents.
How it fits in Microsoft’s agent stack
Five products you’ll see repeatedly at Build 2026:
| Layer | Product | What it does |
|---|---|---|
| OS runtime | Windows Agent Runtime | Local agent registration, discovery, execution |
| SDK / framework | Microsoft Agent Framework | Build agents in .NET / Python |
| Cloud runtime | Windows 365 for Agents | Run agents in secure managed Cloud PCs |
| Distribution | Windows Agent Store | Discover and install agents |
| Authoring & enterprise | Microsoft Foundry / Copilot Studio | Visual agent design, governance, deployment |
| Embedded | Copilot agent mode | Copilot itself acts as an agent |
The mental model: Foundry is where you design and govern agents. Agent Framework is what you code them in. Windows Agent Runtime is where they execute locally. Windows 365 for Agents is where they execute in the cloud. Windows Agent Store is how end users find them.
What’s not in the June 2026 preview
Important caveats — anyone planning around the runtime should know what’s missing:
- No vision agents. No screen-pixel understanding, no GUI automation. (Anthropic’s computer use and OpenAI’s Operator-style agents do this; Microsoft has not yet committed to a vision-agent model on Windows desktop.)
- No multimodal IO. Text and structured data only. Audio, images, video deferred.
- No mobile. Windows-only — no Mac, no Android equivalent. The closest competitor product is Apple Intelligence’s app intents + Shortcuts, plus Android’s Gemini-on-device agents.
- Limited initial agent catalog. The Agent Store opens at preview, but stocking it is a developer-ecosystem project that will take quarters.
Comparison to the field
Quick reference for how Windows Agent Runtime sits vs the rest:
| Platform | Where it runs | Vision | Open SDK | Status |
|---|---|---|---|---|
| Windows Agent Runtime | Windows desktop | Not in June 2026 preview | Yes (Agent Framework) | Insider preview June 2026 |
| Apple Intelligence + App Intents | Mac, iPhone, iPad | Limited (screenshot share) | Yes (Swift) | GA |
| Gemini on Android | Android phones / tablets | Yes (screen sharing) | Limited | GA |
| ChatGPT Atlas | Browser (cross-platform) | Yes (browser DOM + screen) | No | GA |
| Claude Computer Use | Linux/macOS/Windows via API | Yes (screen pixel) | Yes (API) | GA |
Microsoft’s choice to start text-only on structured data is the most conservative of the lot — and probably the most defensible from an enterprise security review.
Who should care now
- ISVs and enterprise dev shops — start building Agent Framework prototypes now. Microsoft will heavily promote Agent Store apps at GA.
- IT admins — start thinking about agent governance policy. Purview audit and Intune control rollout begins at preview.
- Consumer Windows users — no action needed yet; consumer-friendly agents will arrive after Insider previews stabilize.
- Cross-platform teams — note that Windows Agent Runtime is Windows-only. Cross-platform agentic strategies need a separate plan for Mac and mobile.
Quick FAQ recap
- Ship date: June 2026 Insider preview. GA unannounced.
- Scope: Text agents on JSON/XML/PDF. No vision yet.
- SDK: Microsoft Agent Framework (.NET + Python, open source).
- Models: Pluggable — Claude, GPT, Gemini, local.
- Cloud sibling: Windows 365 for Agents.
Verdict
Windows Agent Runtime is the most ambitious enterprise-grade move on agents from any OS vendor in 2026. The text-only, structured-data scope of the June preview is deliberately conservative — Microsoft is shipping plumbing it can govern, not vision-agent features it can’t audit yet. For ISVs and enterprise dev shops, the Agent Framework SDK is worth investment now. For everyone else, watch Build 2026 keynotes June 2–3 for the full picture; this is the foundation of Microsoft’s Windows-as-agent-platform strategy and is likely to define the agentic computing surface on Windows for the next decade.
Sources: Microsoft Build 2026 conference page, PCMag Build 2026 preview, Windows News Build 2026 coverage, Windows Forum analysis, Microsoft Agent Framework GitHub (github.com/microsoft/agent-framework), Tom’s Guide Build 2026 preview (verified May 31, 2026).