A run is the durable execution container. A response is one unit of agent work inside that run.

​
Ownership

ObjectOwns
DeploymentImmutable agent and sandbox configuration
RunConversation, workspace, active sandbox and applied deployment
ResponseOne requested turn and its output state
SandboxReplaceable compute for the run

​
Response states

StatusMeaning
queuedAccepted and waiting to start
in_progressProvider or tool execution is active
completedResponse completed and required durability work succeeded
failedResponse execution or required post-turn work failed
cancelledResponse was intentionally cancelled
incompleteExecution stopped without a complete response

​
Run and response states can differ

A response can complete successfully and the run can later become stopped or cancelled during cleanup. Salambo interprets this case as: 
responses completed, then the run stopped
This is not a failed response. The run status describes the execution container; response statuses describe customer-requested work. Any failed or incomplete response prevents the success-plus-cleanup interpretation.

​
Cancellation

Cancel a response when the client no longer needs active work: 
POST /api/v1/responses/{responseId}/cancel
Cancel a run when the run itself should stop: 
POST /api/v1/runs/{runId}/cancel
Cancellation:
  • aborts active provider work;
  • clears queued steering and follow-up messages;
  • settles the runtime lifecycle;
  • stops active sandbox compute through run cleanup.
Terminal responses and runs cannot be cancelled again.

​
Deletion

Deletion is cleanup for terminal records. Do not use deletion as a substitute for cancellation of active work.