# div runs

> The org's runs, newest first, one line each — what each is on, what it costs per hour while it runs, and what it has spent.

```bash
div runs
div runs --status active
div runs --project very-cool-classifier --limit 10
```

```text
run-8f2a  running          4× H100  $19.80/h   $0.33  1m 0s    very-cool-classifier
run-k4t9  budget exceeded  1× H100         —   $5.00  1h 1m    very-cool-classifier
run-q1b7  succeeded        1× H200         —   $1.05  10m 35s  lora-sweep
1 run holding hardware, $19.80 per hour
```

One line per run: name, status, hardware, the hourly rate while it is still running, what it has spent, the time on the meter, and the project. A finished run shows a dash for its rate, since it has stopped paying it.

The rows go to stdout with no header, so the first column is a run's name and nothing else. The last line, what the unfinished runs cost together per hour, goes to stderr and stays out of a pipe:

```bash
div runs --status active | cut -d' ' -f1 | xargs -n1 div stop
```

## Flags

| Flag | What it does |
| --- | --- |
| `--status <status>` | `active`, `queued`, `provisioning`, `running`, `succeeded`, `failed`, `canceled`, `budget_exceeded` or `limit_reached` |
| `--project <slug>` | only this project's runs |
| `--limit <n>` | how many (default 50, max 500) |
| `--json` | print the runs as JSON, as the API sent them |

`active` means any run that has not finished: queued, provisioning or running. A status that is not on the list exits 2 and names the list. The API would answer it with an empty list, and an empty list reads like good news.

## Every project, unless you say otherwise

`div run` takes its project from the directory you are in. `div runs` does not: without `--project` it lists the whole org, because a run left going in another project costs money too.