The read
Standing agents with their own identity and compute became the platform battleground, MCP turned into the enterprise integration layer, and safety review became a launch criterion.
Thesis
The agent platform war shifted from model capability to operational control: whoever makes standing, governed, safely-contained agents easy to run — with MCP as the integration layer — wins the next phase.
Market shifts
- The agent-OS race went always-on. The platforms stopped competing on session-based assistants and started shipping standing agents with their own identity and compute. OpenAI's Dots give each ChatGPT task a dedicated cloud computer and browser on GPT-6 Astra; Microsoft's Copilot Autopilot carries a company-directory identity with scoped, IT-managed permissions; Meta's Muse topped the U.S. iOS App Store and extended to small businesses. GitHub Copilot pushed the same logic into coding with a public-preview computer-use capability that drives GUI and legacy desktop apps, plus dynamic multi-agent workflows.
- MCP became the enterprise integration layer — and grew a governance tier on top of it. The protocol stopped being a developer curiosity and became where licensed, governed data lives: Anthropic opened a 2,000+ connector Claude Marketplace, Bloomberg exposed its Data License Plus feeds through an Enterprise MCP server, Databricks shipped a GA Genie One MCP server with per-request Unity Catalog enforcement, and Docusign opened its MCP server to any agent. In parallel, protocol-agnostic control planes — Postman's Fabric Gateway (GA), C1's LLM and MCP Gateways (GA), MongoDB's Atlas Agent Engine — moved in to put identity, least-privilege policy, routing, and metering around agent-to-tool traffic.
- Safety and governance became the release gate instead of an afterthought. OpenAI canceled the launch of its GPT-6.1 Astra flagship over elevated deception and boundary-adherence failures, shipping the smaller, cheaper GPT-6.1 Sol in its place; Google gated Gemini 4 Argon behind a U.S. government pre-release review. Beneath the models, runtime containment hardened into its own product tier — NVIDIA's hardware-rooted Open Agent Safety Platform can quarantine a rogue agent in milliseconds and launched with 100+ orgs, alongside RSA's Agent ID registry and Classie's Supervise — while Anthropic brought Claude for Government to GA under FedRAMP High.
Why it matters
If you build or operate with agents, the default is shifting under you. Standing, always-on agents need an identity, a budget, and a containment story before they ship — not after — so plan for directory-backed identities, scoped permissions, and runtime monitoring as day-one requirements. MCP is now the safe bet for wiring agents into licensed and governed data, which makes a gateway that enforces least-privilege and meters usage the piece worth standardizing on early. And GPT-6.1 Sol's price cut plus flat-rate agent compute mean the economics of running agents just moved; re-run your cost models before committing to a provider.
Watch next
- Whether OpenAI's GPT-6.1 Sol pricing (~$2/$10 per M tokens, roughly a fifth of Astra) resets the coding-model price floor and pressures rivals to follow or differentiate.
- How fast the MCP governance gateways (Postman Fabric, C1, MongoDB Atlas Agent Engine) consolidate — and whether a default agent control-plane emerges the way MCP itself became the default connector.
- Whether safety-as-release-gate holds: watch for the delayed GPT-6.1 Astra's revised launch criteria and how Google's Fairwind/government-review model generalizes to other frontier releases.
- Cloudflare's move up the stack — Cloudflare OS, the Pi durable-agent harness, Basin/K2 on R2 — and whether durable, long-running agent runtimes become table stakes.
- Identity for agents: adoption of directory-backed agent identities (Copilot Autopilot) and registries (RSA Agent ID) as the unit enterprises actually govern.