# Track and resume a run

Every run receives a short tracking link when it starts. The same link shows progress and opens the clip when it is ready.

## Two parts of generation

**Local investigation:** keep the process running while Codeclip explores the repository and prepares the technical report.

**Cloud generation:** after the report is submitted, Codeclip creates the narration and animations independently. You can close the terminal at this point. `--wait` keeps following the run until it finishes.

## Check your clips

```sh
codeclip jobs
```

Agents and scripts can use `codeclip jobs --json` and match the exact `clipId` from their run. The tracking page also shows progress and generation errors.

## Resume an interruption

The CLI saves the run directory and prints recovery instructions when possible:

```sh
codeclip resume /absolute/path/to/run-directory --wait
```

For agents:

```sh
codeclip resume /absolute/path/to/run-directory --json --wait
```

Resuming uses the saved request ID and does not reserve another free clip. Do not repeat `generate` as a recovery step: that creates a new run.

## When a retry needs more attention

An interrupted connection may be recoverable. Missing repository evidence or an invalid brief needs investigation before retrying. Resume does not automatically restart every failed cloud stage; report the error and tracking link if the run cannot continue.

If your local process disconnects after submission, the cloud run may still be healthy. Check its status before taking further action.