Skip to main content
Orchestrated benchmarks let you run full benchmark suites or sets of scenarios with a single command. Runloop handles all the complexity: provisioning devboxes for each scenario, running your agents, scoring results, and aggregating outputs. You can compare multiple agents side-by-side, run hundreds of scenarios in parallel, and walk away while the job completes in the cloud.
Orchestrated benchmarks are the recommended way to run benchmarks on Runloop. For fine-grained control over individual scenario runs, see Interactive Benchmarks.

Prerequisites

Before running orchestrated benchmarks, you need:
  1. Runloop CLI installed: Install via npm, yarn, or pnpm:
  1. API key configured: Set your Runloop API key:
  1. Agent configuration: Orchestrated benchmarks work with any agent that can run on a Runloop devbox. You have two options:
  • Bring your own agent: Deploy your own agent to run on Runloop devboxes. This is the most common approach for teams developing proprietary agents. Contact us at support@runloop.ai for help setting up your custom agent.
  • Use a supported public agent: Run benchmarks with popular, public open-source agents. Set up the required API keys as environment variables on your local machine, and the CLI will automatically create secrets:
Are we missing an agent you need? Contact us at support@runloop.ai to request support for a new public agent.

Quick Start

Run a benchmark with a single command:
This command:
  1. Creates a benchmark job with the specified agent and benchmark
  2. Provisions a devbox for each scenario in the benchmark
  3. Runs the agent on each scenario in parallel (by default, 10 scenarios are executed concurrently)
  4. Scores the results automatically
  5. Collects and aggregates all results into the UI

Running Benchmark Jobs

Basic Usage

Run a single agent against a benchmark:

Comparing Multiple Agents

Compare multiple agents side-by-side by specifying multiple --agent flags:
Each agent runs independently against the full benchmark, and results are aggregated for easy comparison.

Running Specific Scenarios

Instead of a full benchmark, you can run specific scenarios by ID:

Controlling Parallelism

By default, benchmark jobs run 10 scenarios concurrently. Increase parallelism for faster execution:

Setting Timeouts

Configure agent timeout (in seconds) for long-running scenarios:

Passing Environment Variables

Pass additional environment variables to the agent:

Using Secrets

Reference Runloop secrets for sensitive values:

Monitoring Jobs

Watch Live Progress

Monitor a running job with a full-screen progress display:
This shows real-time updates as scenarios complete, including pass/fail status and running totals.

List Jobs

View recent benchmark jobs:
Filter by time range or status:

Viewing Results

Summary Report

Get a summary of results after a job completes:

Extended Results

View individual scenario results with the -e flag:

Output Formats

Export results as JSON or YAML for programmatic processing:

Downloading Logs

Download devbox logs for debugging:

Supported Agents

Orchestrated benchmarks support the following agents: Specify the agent and model in the format agent:model:

Supported Benchmarks

Orchestrated benchmark jobs work with any benchmark available on Runloop, including:
  • SWE-bench Verified
  • Laude Institute/Terminal-Bench-2.0
  • ScaleAI/SWE-Bench Pro
  • AIME
  • ARC-AGI-2
  • bigcodebench
  • BigCodeBench-Hard (instruct)
  • BigCodeBench-Hard (Complete)
  • ReplicationBench
  • GPQA Diamond
  • Aider/Polyglot
  • Replication Bench
View available benchmarks:
You can also run your own custom benchmarks via orchestrated mode.

Command Reference

rli benchmark-job run

Create and run a benchmark job.

rli benchmark-job watch

Watch benchmark job progress in real-time.

rli benchmark-job summary

Get benchmark job results.

rli benchmark-job list

List benchmark jobs. Valid statuses: initializing, queued, running, completed, failed, cancelled, timeout

rli benchmark-job logs

Download devbox logs for a benchmark job.

Best Practices

  1. Start with a small subset: Test your configuration with a few scenarios before running a full benchmark.
  2. Use meaningful job names: Name your jobs descriptively to make them easy to find and reuse later.
  3. Monitor long-running jobs: Use rli benchmark-job watch to track progress, or check back with rli benchmark-job list.
  4. Export results: Use -o json to export results for analysis or CI/CD integration.
  5. Tune parallelism: Increase --n-concurrent-trials for faster execution, but be mindful of rate limits on external APIs.

Next Steps