KDCube
← AI Industry News

Agent Runtimes Grow a Persistence Layer: 14-Day Sessions, Stateless MCP

AWS made Bedrock AgentCore runtime instances generally available, giving agents EC2-backed sessions that persist up to 14 days with GPU and multi-agent support. Meanwhile the 2026-07-28 MCP spec goes stateless and Microsoft Agent Framework 1.13.0 deepens hosted, replayable agents — the...

Highlights

  • AWS made Amazon Bedrock AgentCore runtime instances generally available, adding EC2-backed compute that keeps agent sessions alive for up to 14 days — versus the 8-hour ceiling on the default serverless microVM runtime. (AWS)
  • The instances open the full breadth of EC2 families — GPU-accelerated, memory-optimized, compute-optimized — to long-running, multi-agent workloads while AWS handles provisioning, patching, and lifecycle. (AWS News)
  • The 2026-07-28 MCP specification goes stateless at the core, dropping protocol sessions and the Mcp-Session-Id header so any server instance can answer any request behind ordinary HTTP. (Model Context Protocol)
  • Microsoft Agent Framework 1.13.0 lands with richer Foundry hosting and Responses support, reusable session stores, and stronger workflow replay and approvals. (Microsoft)

Key Signals

  1. AgentCore runtime instances hit GA — persistence becomes a runtime primitive AWS, ~Aug 6

    AWS's new instances let multiple agents share a single host and collaborate inside sessions that persist up to 14 days, targeting sustained, resource-intensive, or specialized-hardware work that blew past the serverless 8-hour limit. It reframes "agent runtime" from a request handler into a managed compute platform with real lifecycle management. (AWS, AWS News)

  2. MCP goes stateless — and the SDKs already speak it Model Context Protocol / Google, late Jul–early Aug

    The 2026-07-28 spec removes session pinning, adds cacheable list results and header-based routing, and deprecates the legacy HTTP+SSE transport on a year-long offramp. Google's guidance shows the payoff: MCP servers now run on plain round-robin load balancers and scale to zero on Cloud Run, with no Redis session store at the gateway. (Model Context Protocol, Google)

  3. Microsoft Agent Framework 1.13.0 doubles down on hosted, replayable agents Microsoft, Aug

    The release deepens Foundry hosting and Responses integration, adds reusable session stores, expands telemetry, and hardens workflow replay and human approvals — pushing the AutoGen/Semantic Kernel successor further toward stateful, auditable production deployments. (Microsoft)

Why It Matters / What To Watch

  1. Long-running agents change your cost and failure model.
    • If you run sustained or GPU-bound agents, price the AgentCore management fee on top of EC2 and design for 14-day sessions as a new failure surface — checkpoints and idempotency matter more the longer a session lives. (AWS)
    • Watch whether persistent-host pricing favors consolidating many agents per instance versus the pay-per-invoke microVM path. (AWS News)
  2. Stateless MCP is a migration, not just a spec bump.
    • Audit connectors that rely on Mcp-Session-Id or HTTP+SSE; the transport is deprecated with a one-year offramp, so plan the cutover now rather than at the deadline. (Model Context Protocol)
    • If MCP servers were pinned behind sticky routing, the stateless core lets you drop session stores and scale to zero — revisit gateway and load-balancer configs. (Google)
  3. Hosting is becoming the framework's job.
    • Reusable session stores and built-in replay/approvals in Agent Framework 1.13.0 mean less bespoke persistence glue — evaluate whether framework-native hosting can retire your custom state layer. (Microsoft)

Quick Links