Console consumes the same control-plane API; it is not an independent execution backend. Closing it does not stop tasks.
Authorization, approval, and unknown remote outcomes add waiting and reconciliation branches. This diagram does not assume every remote operation returns a response.
Follow one project task across the boundaries
Suppose your backend asks an Agent to add a filter to an uploaded project, run its tests and export the changed files. Your backend owns the business request and its association with the user. The control plane owns the Session and Run records. The cloud Sandbox holds the working files and processes; Runtime supervises the Harness, which chooses how to perform the task. The arrows describe responsibility and data flow, not one listener or one network connection. The control plane’s management API, protected credential ingress and private Runtime access have different authentication and reachability requirements. A Provider connector runs on the control-plane side; it is not an Agent process in the guest. For this task, a successful model response is only one observation. The Harness must still finish execution; the worker interprets its output and captures exported artifacts before completing the Run. The current artifact implementation stores metadata and bytes in PostgreSQL. Unexported workspace files remain subject to the selected Sandbox’s persistence behavior. Closing the Session cleans up cloud resources while retained Run records and exported artifacts remain queryable.Two deployment locations, the same execution boundary
Local control plane
The SDK’s supported local discovery identifies the local workspace endpoint and client credentials. The guest still runs in the cloud. A loopback management URL on your laptop is not a cloud-reachable credential endpoint: configure the separate development ingress required by the chosen execution path. Shutting down the local control plane stops its workers and reconciliation; it does not by itself prove that every remote process or resource has stopped.Hosted control plane
Hosted changes where the control plane and its durable services run. It does not move Harness execution into the API server. Your application backend still authorizes business users and protects its control-plane Token. Both deployments need a supported Sandbox/Harness/model combination; neither topology claims every catalog entry has passed the same real-cloud journey.Where resources and credentials belong
Model traffic uses protected credential access; the Harness still chooses a compatible model protocol. That access backend does not convert protocols or decide whether a task succeeded. Brokered Tools use a different path: the Harness submits a request through the Runtime bridge, the worker asks the control-plane broker to authorize/approve/dispatch it, and the result returns through the bridge. A permitted external write can occur without revealing its original credential to the Agent.
This description applies to Hexagon-managed connections and brokered Tools. Native shell commands and network requests made by task code are also subject to the configured Sandbox/network boundary; do not assume every arbitrary command is intercepted for human approval. See credential and trust boundaries for delegated authority, registry auth and ordinary variables.