---
title: Run
order: 7
description: "One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate."
tags: [glossary, sessions-and-leases]
---

# Run

One target executing under one `magus` invocation, such as `magus run test web`
or `magus affected ci`. A run keeps its captured output behind an output
reference. Every `magus run` is a run whether or not any job asked for it; see
Job for how the two relate.

## Elsewhere

In GitHub Actions a workflow run contains jobs. In magus the containment goes the other way:
a job causes runs, and most runs belong to no job.

## Example

```sh
magus run test web
```

## Used in

<!-- BEGIN GLOSSARY USAGE (generated by glossary-usage-generate from the knowledge graph; edit the generator, not this list) -->

In the docs:

- [S3: Affected dry-run (1 file changed)](../benchmarks/build-tools.md#s3-affected-dry-run-1-file-changed)
- [Tools that run their own jobs: the jobserver](../concepts/concurrency.md#tools-that-run-their-own-jobs-the-jobserver)
- [Both-arms rule: the static graph and a dry run can disagree](../concepts/dependencies.md#both-arms-rule-the-static-graph-and-a-dry-run-can-disagree)
- [One provider per run, and why there is no fallback chain](../concepts/secrets/providers.md#one-provider-per-run-and-why-there-is-no-fallback-chain)
- [docker-run](../concepts/spells/docker.md#docker-run)
- [go-run](../concepts/spells/go.md#go-run)

In the code (`magus refs <name>` lists every site):

- `forecast.Run` (Go)
- `screen.run` (Go)
- `queue.run` (Go)
- `magus.run` (Go)
- `rankeval.Run` (Go)

<!-- END GLOSSARY USAGE -->

## See also

- [Job](job.md)
- [Output reference](output-reference.md)