# Work from the terminal

> Inspect, validate, preview, and run a Renart pipeline from the command line.

Use the Renart CLI when you want the same pipeline model in a shell, script, or CI job. Commands discover the project by walking up from your current directory, the same way Git does.

## Before you start

- [Install Renart](https://getrenart.com/docs/installation.md).
- Open a terminal anywhere inside a Renart project.

## Inspect and validate the project

List the available assets, then type-check the pipeline before you execute anything:

```bash
renart ls assets
renart type-check retail
```

Type-check validates dependencies, SQL columns and types, declared output schemas, materialization settings, and custom SQL checks. Add `--strict` in CI when warnings should also fail the job.

[Interactive terminal recording that lists assets, type-checks a pipeline, and reviews its execution plan](https://getrenart.com/cli-recordings/workflow.cast)

## Review what would run

`plan` explains the selection, readiness, execution units, and operation count without writing to a warehouse. It plans assets that need work by default:

```bash
renart plan retail
renart plan retail --all
renart plan retail --selector 'tag:daily,+analytics.daily_revenue'
```

Use `render` when you need the exact preview for one asset:

```bash
renart render analytics.daily_revenue
renart render analytics.daily_revenue --json
```

[Interactive terminal recording of an asset render preview](https://getrenart.com/cli-recordings/render.cast) The preview separates compiled SQL, setup operations, and execution SQL without running them.

## Execute the pipeline

Run the whole pipeline, one asset, or an asset plus its downstream dependents:

```bash
renart run retail
renart run analytics.daily_revenue
renart run analytics.customer_orders --downstream
```

When the workspace already has this project open, the command delegates to that local server so Runs, freshness, and results update immediately. Otherwise the command runs locally. Use `--json` for JSON Lines events or `--quiet` for a concise CI result.

> **Caution**
>
> `renart run` writes to the selected environment. Review `renart plan` first, especially before `--full-refresh`.

## Deploy a schedule snapshot

After you review the current working tree, snapshot the pipeline version used by scheduled runs:

```bash
renart deploy retail
```

## Result

You can inspect and validate a project, review exact operations, execute a selection, and deploy a schedule snapshot without leaving the terminal.

## Related

- [CLI reference](https://getrenart.com/docs/reference/cli.md)
- [Runs and history](https://getrenart.com/docs/workspace/runs-and-history.md)
- [How Renart works](https://getrenart.com/docs/how-it-works.md)