RunExecution

What the device that answered can do about the run, and what it holds (D3, D15, §7.4).

Deliberately not a header field: the header is what a run means on every device, and how far this machine got is execution state. A surface compares [Self::device] with the header's executing device to decide whether it may offer an action at all, and takes control through [Self::session] when there is one.

Type object

Shape

Field	Type	Description
devicerequired	string	The device whose worker answered.
session	TerminalSessionId or null	The provider session of the attempt this device is driving right now. `None` everywhere else - on another device, between attempts, and after the run ended - and a surface offers no handover without it.
run_workspace	string or null	The folder the agent is working in, as this device resolved it. A scope says what kind of folder was asked for - a project's root, a folder inside one, or one Koru makes - and only the device driving the run knows which one that turned out to be. A person judging a run they did not watch is entitled to be told where it happened. `None` on a device that is not driving it, and before an attempt has one. It is a path, so it is a person's own and stays on this wire: it reaches no log, no event attribute and no metric (§13.7).

Example

{
  "device": "string",
  "session": "00000000-0000-4000-8000-000000000000",
  "run_workspace": "string"
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Generated from contract version 1. Last updated November 12, 2026.