The story this week is the agent runtime perimeter moving. At Code with Claude London on May 19, Anthropic shipped self-hosted sandboxes in public beta and MCP tunnels in research preview: the tool-execution layer of a Claude Managed Agent can now run inside your network on your own infrastructure (or via Cloudflare, Daytona, Modal, or Vercel) while the agent loop itself - orchestration, context management, error recovery - keeps running on Anthropic's servers. Files and repositories no longer leave the customer perimeter.

Two days later, on May 21, the next MCP specification release candidate locked. The Mcp-Session-Id header is gone, the protocol layer is fully stateless, and any MCP request can now land on any server instance - sticky routing and shared session stores are no longer protocol requirements. The RC also lands the Extensions framework, Tasks, MCP Apps, authorization hardening, and a formal deprecation policy. The final spec publishes 2026-07-28; SDK maintainers have a 10-week window to validate.

Different timelines, same direction: the architectural baggage that made agent infrastructure feel borrowed is getting torn down. The enterprise side moved with it - KPMG put Claude in front of 276,000 people via the new Digital Gateway alliance, also announced May 19.


From us

Anthropic this week

MCP this week

Claude Code this week

The broader week