AI agents · OpenClaw · self-hosting · automation

Quick Answer

Windows Agent Runtime vs Apple Intelligence vs Android Gemini

Published:

Windows Agent Runtime vs Apple Intelligence vs Android Gemini (May 2026)

Three OS-level AI agent platforms, three different bets on what “the operating system as agent platform” means.

Last verified: May 31, 2026.

TL;DR

PlatformBest for
Windows Agent Runtime (Microsoft)Enterprise agents with policy controls, audit, Microsoft 365 integration. Most ambitious but earliest stage (June 2026 preview).
Apple Intelligence (Apple)Consumers in the Apple ecosystem who want privacy, on-device, deep cross-device sync. Most conservative capability set.
Android Gemini Intelligence (Google)Broadest hardware reach, strongest screen-understanding, on-device Gemini Nano plus cloud Spark. Best for general consumer AI assistant.

What each one actually is

Windows Agent Runtime

A new OS-level platform layer Microsoft is shipping in Insider preview in June 2026, announced at Microsoft Build 2026 (June 2–3, Fort Mason SF). The platform:

  • Lets apps register agents through Windows APIs.
  • Routes invocations between apps and agents.
  • Sandboxes execution with enterprise policy (Intune, Purview).
  • Ships an open-source SDK (Microsoft Agent Framework, .NET + Python).
  • Supports any model — Claude, GPT, Gemini, local.

Initial scope is intentionally narrow: text-only agents on JSON/XML/PDF. Vision-based agents (screen-pixel understanding) are deferred to a later release. Companion products: Windows 365 for Agents (cloud PCs for agent workloads), Windows Agent Store (distribution), Copilot agent mode (consumer surface).

Apple Intelligence

Apple’s OS-level intelligence layer, GA across macOS, iOS, iPadOS, and visionOS. The platform:

  • Routes most queries through on-device models (Apple’s Foundation Models, including a vision model and an LLM).
  • Escalates harder queries to Private Cloud Compute (Apple’s hardened cloud infrastructure with cryptographic attestation).
  • Optionally routes to ChatGPT, Claude, or Google via per-request extensions (user-confirmed).
  • Integrates with App Intents and Shortcuts as the agentic invocation surface.

Agent capability is conservative — App Intents let apps expose actions Siri and Apple Intelligence can call, but full autonomous multi-step agents are still rare. The May 2026 wave brings deeper App Intents for Mail, Calendar, Photos, plus stronger Visual Intelligence on macOS.

Android Gemini (Gemini Intelligence)

Google’s deeply-integrated AI layer across Android, GA. The platform:

  • Runs Gemini Nano on-device for low-latency local inference (summarization, reply suggestions, on-device privacy).
  • Routes to Gemini 3.5 Flash in the cloud for harder queries.
  • Powers Gemini Spark — Google’s always-on personal agent ($100/mo AI Ultra in US, May 30, 2026 launch).
  • Strong screen-sharing and screen-understanding capabilities.
  • Spans the broadest hardware footprint of any agent platform — phones, tablets, ChromeOS, Wear OS, Android Auto, Google TV, and Gemini-for-Home.

Side-by-side

DimensionWindows Agent RuntimeApple IntelligenceAndroid Gemini
Status (May 2026)Insider preview June 2026GAGA
Hardware reachWindows 11/12 desktops, Windows 365 cloud PCsMac, iPhone, iPad, Vision ProAndroid phones/tablets, ChromeOS, Wear, Auto, TV, Home
On-device modelsYes (Windows Copilot Runtime)Yes (Apple Foundation Models)Yes (Gemini Nano)
Cloud fallbackAzure AI Foundry, any providerPrivate Cloud Compute + ChatGPT/Claude extensionGemini 3.5 Flash, Spark
Screen/vision agentNot in June previewLimited (Visual Intelligence)Strong (screen share to Gemini)
Cross-app agent registryFirst-class (Agent Framework)App Intents / ShortcutsApp Actions, intents
Enterprise governanceFirst-class (Intune, Purview)MDM-managedWorkspace + Endpoint Mgmt
Pluggable modelsYes (Claude, GPT, Gemini, local)Limited (per-request opt-in)Google models only (mostly)
Always-on personal agentNo (not yet)NoYes (Gemini Spark)
Open SDKMicrosoft Agent Framework (open)App Intents (Swift, closed runtime)Limited

Where each one wins

Windows Agent Runtime wins when…

  • You’re building for enterprise Windows fleets with strict governance, audit, and policy.
  • You want a cross-app agent registry so agents can invoke each other without bespoke integrations.
  • You’re already on Microsoft 365 + Foundry + Azure and want the agent layer to align.
  • You can wait for the June 2026 preview and tolerate text-only-structured-data scope.

Apple Intelligence wins when…

  • Your users live in the Apple ecosystem and value cross-device continuity (Handoff, iCloud, Continuity Camera).
  • Privacy posture matters — Apple’s on-device + Private Cloud Compute is the strongest privacy story.
  • You’re shipping a consumer app where deep OS integration (Siri, Shortcuts) matters more than agent depth.
  • Your agent needs are conservative — augmentation rather than autonomous multi-step work.

Android Gemini wins when…

  • You want the broadest hardware reach — phones plus tablets plus ChromeOS plus Auto plus TV plus Home.
  • Screen understanding matters — Gemini can see what’s on screen and act on it natively.
  • You want an always-on personal agent today — Gemini Spark is GA (US AI Ultra) as of May 30, 2026.
  • You’re already invested in the Google Workspace stack.

The cross-platform problem

If you’re building an agent that should work on Windows, Mac, and Android — none of the three platforms makes this easy. The practical pattern in May 2026:

                Agent core (Anthropic / OpenAI / Google API + tools)

                ┌───────────────────┼───────────────────┐
                │                   │                   │
        Windows adapter      Mac/iOS adapter     Android adapter
    (Agent Framework +     (App Intents +       (Gemini System
     Windows Agent          Shortcuts +          Services +
     Runtime invocation)    SiriKit)             Intents)

Build the agent core once on top of an LLM API (or Microsoft Agent Framework — it’s open source and the most portable of the SDKs). Build per-OS thin adapters for system-level integration. Don’t try to use a single OS-level platform across all three.

What changes at Build 2026

The big question is whether Microsoft’s Windows Agent Runtime + Windows 365 for Agents combination becomes the dominant enterprise agent platform. The argument for: deeper governance than Apple or Google, ISV ecosystem motivation via Agent Store, and integration with the world’s deployed Microsoft 365 base. The argument against: shipping text-only-structured-data first means vision-heavy agentic computing (which is where consumer wow factor lives) is deferred.

Watch Nadella’s June 2 keynote for the framing, then the Build 2026 sessions on Agent Framework, Foundry, and Windows 365 for Agents for the technical depth.

Quick decision tree

Where do your users live?
├── Windows enterprise → Windows Agent Runtime + Foundry + 365 for Agents
├── Apple consumer → Apple Intelligence + App Intents
├── Android consumer → Gemini Intelligence (+ Spark if always-on agent)
└── Cross-platform → Anthropic/OpenAI/Google API + per-OS adapters

Verdict

No single OS-level agent platform wins in May 2026. Microsoft is most ambitious on enterprise governance and cross-app registry but is earliest stage. Apple is strongest on privacy and on-device but most conservative on agent capability. Google has the broadest reach and strongest screen-understanding but is least open. For pure platform bets, watch Microsoft Build 2026 — Windows Agent Runtime is the most strategically important agent-platform announcement of the year. For shipping cross-platform agents today, the right answer remains: build on an LLM API, integrate per-OS where it matters, and don’t lock in to one platform’s runtime yet.

Sources: Microsoft Build 2026 conference page, Windows News Agent Runtime preview coverage, Apple Intelligence developer docs (developer.apple.com/apple-intelligence), Google I/O 2026 Gemini Intelligence keynote, PCMag Build 2026 preview, Yaabot Gemini Intelligence Android guide, Help Net Security Windows 365 for Agents coverage (verified May 31, 2026).