Skip to content
VECTOR WIREAI INTELLIGENCE
UTC
Home

Agent stack stratifies as control-plane layer stays underbuilt

ANALYSIS The agentic AI stack is splitting into three distinct layers, and the seam that matters most right now is the one nobody ships as a finished product: the control plane that decides whether an agent's proposed action is actually permitted. A wave of new orchestration products, enterprise governance platforms, and multi-agent coordination tools all claim pieces of this layer, but each approaches it from a different direction, leaving the authority question unresolved.

Why it matters

Enterprises face an 80-point gap between experimentation and production: Cisco RSA 2026 data shows 85% of customers experimenting with agentic AI but only 5% in production13. OutSystems cites developer survey data showing that 74% of AI-generated code requires significant rework after generation or is never deployed to production7,9. That gap is not primarily a model problem; it is an architectural problem rooted in the absence of a unified layer governing routing, state, permissions, and recovery across heterogeneous agent deployments, and the latest product launches are racing to fill it from opposite ends.

The big picture

The industry has reached consensus on what an agent needs to run: shell access, file manipulation, web tools, and long-term memory15. AWS, DigitalOcean, and Aiven shipped agent harnesses in the same week that LangChain Interrupt 2026 in New York City confirmed the same pattern at the framework layer. The harness, as defined by OpenAI's Codex platform post of August 19, 2026, manages conversation state, streams execution, uses tools, enforces sandbox and approval policies, and carries work across turns16. Anthropic's Claude Agent SDK exposes "the same tools, agent loop, and context management that power Claude Code"17. Microsoft Agent Framework reached 1.0 GA in April 2026.

Below the harness sits the protocol layer. Model Context Protocol, which began at Anthropic in late 2024, now records 500 million monthly downloads of its tier-1 SDKs and more than 1 billion MCP tool calls through the Claude platform alone, according to co-creator David Soria Parra, who told a keynote audience in Amsterdam, "I think MCP today is in a pretty reasonable spot"18.

Above both layers, a cluster of new products is staking claims. Cognitum One released Ruflo, an open-source agent meta-harness and multi-agent orchestration platform for Claude Code, Codex, and other MCP clients, claiming 12.5 million npm downloads4,5. Ruflo turns one assistant into a coordinated team of more than 100 specialized agents and adds a "single control plane to orchestrate swarms, intelligence, safety, operations, and extensible networks, with human approval where it matters". Band, the multi-agent collaboration platform from Thenovi AI, launched Band for Developers, a desktop application that lets software engineers manage multiple coding agents at once2. "Developers are going from working with one coding agent to leading teams of them, but the tools around those agents haven't evolved to support that," said CEO Arick Goomanovsky. OutSystems made its Agent Experience generally available, opening its platform to any AI coding agent including Claude Code, Cursor, Codex, and Kiro8. The approach lets external agents shape application architecture while OutSystems handles code generation deterministically. VS Code 1.140, released September 30, 2026, added multi-folder agent sessions, the Copilot harness, and experimental remote delegation that lets agents discover connected hosts and launch sessions based on available resources14.

Between the lines

19How to Build a Control Plane for AI Agentstowardsdatascience.comMedium10·02 11:00Z

The distinction between capability and authority is the crux. "An LLM has a capability when it can select a tool and produce arguments. It has authority only when a separately enforced policy permits a bounded action for an identified principal in the current context"19. Schema validation confirms well-formed input; authentication confirms who presented a request. "None of these things establish that the current principal may cancel that specific subscription that the user meant, that account, or that the cancellation actually took effect".

AWS Bedrock AgentCore, which reached general availability in June 2026, offers a managed agent loop with isolated microVMs per session. Yet it remains a vendor-walled ecosystem, and the meta-orchestration layer that must unify MCP, Agent-to-Agent communication, identity frameworks, sandbox lifecycles, and execution governance "simply does not exist as a cohesive product or standard".

LangSmith Engine monitors production data, clusters failures into named issues, and diagnoses root causes against the developer's codebase. Each new entrant solves a different slice. Ruflo targets mission-driven workflow orchestration with human-approval gates. Band addresses inter-agent coordination and context sharing. None of them yet delivers the full authority layer that the capability-versus-authority distinction demands.

Practitioners are building their own answers. One developer's open-source control plane separates task and risk routing from retrieval, context assembly, and execution, emitting a "bounded orchestration contract" that caps agent-slot limits, graph depth, and verification passes20. Retrieval ends in one of three states: sufficient, requires_exploration, or abstain, and weak evidence can prevent an agent from editing prematurely.

What's next

MCP's governance trajectory under the Linux Foundation's Agentic AI Foundation will shape whether the protocol layer absorbs identity and authorization or leaves that to the control plane above it. AAIF head Mazin Gilbert stated that "you cannot deploy agentic applications at scale without MCP". If MCP expands to cover identity and execution governance, it compresses the space available for standalone control-plane products like Ruflo and Band; if it stays narrow, the control plane becomes the most contested layer in the stack. Soria Parra's cited 500 million monthly SDK downloads and more than 1 billion tool calls give the foundation leverage to set terms for whatever the protocol becomes next.

Was this useful?

The day’s vector, in your inbox.

Vector Wire Daily: one dispatch each publishing day.