Who it is for
SaaS and developer-tool vendors, plus platform teams deciding what to expose to agents and under what isolation and control guarantees.
Why now
In this window the shift appeared in commercial strategy rather than only prototypes: an app builder repositioned its products as agent-callable capabilities behind hosted MCP servers with an organizational agent as the primary interface; a cluster of AI-native projects replaced external pull requests with maintainer-run agent factories, moving the community's role to issues and review; a managed agent computer showed the trade-off of platform-owned hosts (lost control of routing and context); and a UI framework shipped a single typed graph that yields both a drag-and-drop canvas and per-output REST endpoints. A year ago MCP exposure was an experiment; now it is a stated distribution strategy, and the isolation and control costs are being observed.
What would kill it
Enterprise workflows continue to be routed primarily through human-operated UIs, or agent-callable surfaces remain too unreliable for core processes — for example repeated-attempt reliability stays far below single-attempt success — so vendors keep building for people first.