KDCube
← AI Industry News

Managed Agent Runtimes Go GA: Microsoft's Harness, Google's Gemini Stack

Microsoft Agent Framework's agent harness and Foundry Hosted Agents hit general availability, while Google's Gemini Enterprise Agent Platform went GA on July 30 with a 7-day Agent Runtime, Agent Identity, and an Agent Registry. Managed, governed agent runtimes are now table stakes across the clouds, with cryptographic ...

Highlights

Managed agent runtimes go GA across the clouds.

  • Microsoft Agent Framework's agent harness and Foundry Hosted Agents reached general availability, bundling shell/filesystem access, tool-approval gates, context compaction, file memory, and built-in OpenTelemetry into the runtime itself. (InfoQ)
  • Google's Gemini Enterprise Agent Platform went GA on July 30, shipping an Agent Runtime that runs agents continuously for up to 7 days, plus Agent Memory Bank, Agent Gateway, and an Agent Registry to curb agent sprawl. (Google Cloud)
  • Agent Identity arrives as a native IAM type: every agent gets a unique cryptographic ID, least-privilege scoping, runtime-bound tokens, and non-repudiable audit of every action. (Infosecurity)
  • The 2026 MCP roadmap reorganizes the protocol around priority areas — transport scale, Tasks retry/expiry, and enterprise audit/SSO via extensions — rather than fixed release dates. (MCP)

Key Signals

  1. Microsoft's agent harness reaches GA — August 2026, per InfoQ

    The layer where model reasoning meets real execution — function invocation, per-call history, plan/execute todo modes, web search, and tool approval — is now supported and generally available, with GitHub Copilot and Claude Agent SDK connectors routing third-party coding agents through the same identity, content-safety, and observability policies. For platform teams, "run an agent in production" stops being bespoke glue and becomes a governed, consumption-billed target. (InfoQ, Microsoft)

  2. Google's Gemini Enterprise agent stack lands GA — July 30, 2026

    Beyond the 7-day Agent Runtime and structured Memory Bank, Google enforces identity below the application tier: Agent Identity binds access to the agent runtime, Agent Gateway adds Model Armor inline against prompt injection and tool poisoning, and Agent Registry gives admins a single pane to monitor compliance. It's the clearest cross-cloud parallel to AWS AgentCore's persistent sessions and Microsoft's harness. (Google Cloud, Infosecurity)

  3. MCP's 2026 roadmap goes date-free — posted March 9, 2026

    Working Groups now drive their own timelines around four priorities, with enterprise readiness — audit trails, SSO-integrated auth, gateway behavior, config portability — deliberately routed through extensions rather than core spec churn. After the stateless 2026-07-28 spec, the signal is stability over breaking changes. (MCP)

Why It Matters / What To Watch

  1. The managed agent runtime is now table stakes across all three clouds.
    • Compare harness feature parity — approval flows, context compaction, telemetry — against AWS AgentCore and Google's Agent Runtime before betting a fleet on one. (InfoQ)
    • Watch consumption-based billing: Foundry Hosted Agents and Gemini's runtime both price on usage, so long-running (multi-day) agents make cost governance a first-class design concern. (Google Cloud)
  2. Identity is becoming the real governance surface, not dashboards.
    • Plan how you'll map cryptographic agent IDs back to authorization policies that are traceable and auditable — Google is enforcing this at the IAM layer, not the app layer. (Infosecurity)
    • Registries and gateways are the sprawl countermeasure; inventory who can spin up agents and where before that catalog fills itself. (Google Cloud)
  3. Bet on MCP extensions, not core spec changes, for enterprise features.
    • Track the Tasks primitive gaining retry-on-transient-failure and result-expiry semantics — that's what makes durable, resumable agent work portable across servers. (MCP)

Quick Links