ax run

Two id shapes appear below: a run request id covers one ax experiment run submission, and a composite run id (<variant_id>::<hash>) names one run inside it. Platform-backed commands also accept --org <org-id>, and all but run cancel, run cleanup, and run upload accept --json; neither flag is repeated in the tables. Arguments marked required must be supplied; everything else is optional, and flags combine freely unless a row says otherwise.

run list

List runs, one row per run, grouped by status and newest first.

ax run list

That classification lands minutes after a run finishes, so --agent-test-aware never matches a run that is still unclassified, and there is no filter for the opposite verdict. Seeing a classification does not require the flag: whenever any listed run carries one, the table gains a trailing AGENT TEST AWARENESS column, and piped output gains three matching columns. --json rows always carry test_aware, behavior_changed, and awareness_cause, each null until the run is classified.

Examples:

# Errored runs for one experiment
ax run list --experiment my-experiment --status errored

# Local runs only, grouped by variant
ax run list --scope local --group-by variant

run view

View a run request roll-up, or one run in detail with its tests or conversation.

ax run view <RUN_REQUEST_ID | RUN_ID>

Transcript output adapts to stdout. An interactive terminal shows the run summary and a table. A pipe receives headerless TSV in seq, ts, role, kind, text order, with the run summary and completeness notices on stderr. Pass --json for one structured run document with transcript.turns. Transcripts currently require a platform run.

Run status and test outcome are separate signals: a run whose agent finished but whose tests failed is still completed (with a non-green tests line); only infrastructure failures are errored. For request roll-ups the command exits non-zero when any run ended unsuccessfully (setup failure, timeout, cancel); test failures alone do not change the exit code.

When a platform run contains evidence that the agent is aware it is being tested, it is classified as "test aware" and an agent test awareness row appears with the cause and evidence excerpts. Unclassified runs, and runs where the agent did not notice, look unchanged.

Examples:

# Roll-up for a whole submission
ax run view 01KSDQ...

# One run's failing test, with output
ax run view 'claude::p0::abc123' --test report-exists

# One run's dialogue as structured output
ax run view 'claude::p0::abc123' --transcript --json

# Dialogue and reasoning with a raised turn limit
ax run view 'claude::p0::abc123' --transcript --include reasoning --limit 1000

run watch

Poll a run request until it reaches a terminal status.

ax run watch <RUN_REQUEST_ID>

run query

Run read-only SQL scoped to one run: against uploaded platform data, or a local run with --local. Platform test scripts use the separate test-only ax-run-query command; authentication is supplied automatically and limited to that run.

ax run query <RUN_ID> sql "SELECT * FROM test_analysis"

Examples:

# What is queryable
ax run query 'claude::p0::abc123' sql --tables

# Failing tests for one run
ax run query 'claude::p0::abc123' sql \
  "SELECT test_name, exit_code FROM test_analysis WHERE exit_code != 0" --format table

# Conversational evidence inside a platform test (stdout and/or transcript)
ax-run-query "$AX_RUN_ID" sql \
  "SELECT count() AS matches FROM events WHERE source IN ('stdout', 'transcript')"

# Same run, offline
ax run query 'claude::p0::abc123' sql "SELECT * FROM runs" --local

See Tests for a complete transcript assertion.

run rerun

Rerun failed or canceled variants from a prior platform request, or re-run tests only against completed runs with --tests (see Tests).

ax run rerun <RUN_REQUEST_ID>
ax run rerun <RUN_ID> --tests --experiment experiment.yaml

Remote test-only reruns execute against each run's captured sandbox snapshot; if the snapshot was garbage-collected or never captured, the submit is rejected and you should create new runs instead. Tests that query transcript events with $AX_RUN_ID receive the same run-scoped access during a retest. User-triggered test-only reruns do not run the environment's teardown again.

run cancel

Cancel all jobs in a run request, or selected runs within it.

ax run cancel <RUN_REQUEST_ID>

run cleanup

Run a previously skipped or failed declared teardown for one platform run.

ax run cleanup <RUN_ID>

Create a retained platform run with ax experiment run <EXPERIMENT> --no-teardown. When that run finishes, the CLI prints its exact cleanup command. Cleanup runs the declared teardown only. It does not repeat setup, agent execution, or tests, and exits non-zero if teardown fails.

run cleanup operates on the retained platform snapshot for one run. It is different from run clean, which finds orphaned local sandbox containers.

run upload

Upload a local run to the platform so it appears alongside platform runs.

ax run upload [RUN_ID]

run clean

List orphaned local sandbox containers, and remove them with --yes.

ax run clean [--yes]