After Harness, Loop, and Graph, Agents Need a Control Plane
Execution environments, feedback loops, and task graphs explain how agents run. A control plane governs identity, policy, budgets, observability, and termination at scale.
A useful way to decompose agent engineering is Harness, Loop, and Graph. The harness supplies models, tools, permissions, and runtime; the loop observes, acts, receives feedback, and stops; the graph represents dependencies, branches, and concurrency.
Those layers explain how one agent completes a task. They do not answer fleet questions: which of fifty runs takes priority, who may touch production, how budgets are allocated, why failures repeat, or how an organization pauses everything safely.
The missing layer is a control plane. It does not perform the business task. It centralizes identity, policy, quotas, versions, routing, approvals, telemetry, and lifecycle decisions that should not be buried in prompts or application code.
Agents SDK capabilities such as handoffs, guardrails, and tracing, LangGraph's durable execution, and Temporal's recoverable workflows are converging toward parts of this layer. The control plane is the organizational contract across them, not another framework logo.
Identity is the first contract. Every run should identify the user it represents, the service identity it uses, and the permissions it inherited, while narrowing authorization for each child task. Otherwise an audit log records only that a model called a tool.
Budget and termination are the second. Tokens, browser minutes, external APIs, approvals, and retries are real costs. The system needs task-level limits, loop detection, and authority to stop when additional effort no longer adds proportional value.
Observability is the third. Teams need consistent success, latency, cost, and error semantics across models and tools. A shared telemetry vocabulary may ultimately matter more than any single agent framework's proprietary dashboard.
Agent platforms will increasingly resemble cloud platforms: a data plane performs actions while a control plane defines policy and state. Harness, Loop, and Graph remain essential, but governance determines whether they can enter production safely.
— End —