Skip to main content
Execution capabilities belong to an exact runtime and deployment. A configured adapter, protocol connection or source example does not prove that a Workspace can use it. Bring-your-own sandbox-provider integrations are retired; Checkfu’s execution direction is managed or customer-owned Cloudflare.

​
Capabilities are independent

Code execution, browser access, desktop viewing, input, network isolation and persistence are separate capabilities. Request the features the workload needs and check capability status for their maturity, availability and prerequisites. Execution must refuse requirements it cannot satisfy. It must not silently weaken a network policy, substitute an empty machine or promote a file snapshot to process recovery.

​
Control and continuity

Read-only viewing does not authorize input. Human control requires current control authority; old control must be revoked when ownership changes. A Session borrowing a Computer does not own its destruction. Retained history, restored files, native checkpoints and live-process recovery have different guarantees. Only rely on the grade supported by the selected Harness, runtime and retention policy. Neither a checkpoint nor a successful connection proves that an external effect completed. See Environment and execution selection and Security for the requirements that apply to execution.