run_interleaved
Compare two or more versions as matched arms in rotating task blocks so each arm sees every task at nearly the same time, controlling for latency or cost drift; blocks until all arms finish.
Instructions
Run two or more versions as matched arms in rotating task blocks, so each arm sees every task at nearly the same time. Use it for parent-versus-candidate measurements when latency or cost may drift; use run_launch for one arm or a detached run. Blocks until all arms finish. Writes run records, results and traces, and costs whatever the scenario's tasks cost. Repeating the call with identical arms and parameters resumes and skips committed slots; a new plan needs fresh run ids. Returns each arm's run status, keyed by run id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"config": "<config>",
"arms": "<arms>"
},
"name": "run_interleaved"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| arms | Yes | Map of new run id to version id, at least two entries, for example {"parent-1": "<sha256>", "child-1": "<sha256>"}. Run ids are 1 to 80 letters, digits, `_` or `-`, starting with a letter or digit. | |
| seed | No | Integer that rotates which arm starts first in each block. Default 0. | |
| split | No | Task split: `diagnosis` to explore and read failures, `selection` for gate evidence. Default `selection`. Confirmation and final splits are never available. | selection |
| config | Yes | Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path. | |
| repeats | No | Times each task runs, at least 1. Default 1. | |
| workers | No | Parallel task workers, 1 to 256. Default 4. |