Start a benchmark with an installed agent.
The tracker accepts the run and returns its id. Every option, alias, default, and constraint is in the valkyrie run start and client.runs.start reference.
Decide the run scope
A run covers the whole dataset unless you narrow it. Narrow by task id when you know which tasks matter, or by slice for a cheap smoke run:
To select ids explicitly, export the dataset’s task ids first with valkyrie benchmark tasks, then pass them with --task-ids or --task-ids-file.
--concurrency sets how many sandboxes run at once. Raising it shortens wall-clock time and raises simultaneous provider and model cost.
Map secrets instead of passing values
-s maps an environment variable to an AWS Secrets Manager secret name. It never accepts the raw secret value. A CLI mapping overrides the agent contract’s mapping for the same environment variable.
Stream progress as the run starts
Without --connect, attach later with valkyrie run fetch. See Monitor runs for reading the stream.
Start repeated runs
Start requests are sent sequentially. Accepted runs execute independently and may overlap. --connect is rejected when count is greater than 1.
Approximate simultaneous task pressure and cost can scale with count × concurrency.
valkyrie run list.