> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/commands/cos-scan-start.md).

# COS scan start

The snyk cos scan start command that starts a new scan on a target.

{% hint style="info" %}
**Release status**

The `snyk cos` command set is in Closed Beta and is available only for Enterprise plans. If you want to set it up in your Group or Organization, contact your Snyk account team.
{% endhint %}

## Usage

`snyk cos scan start [<OPTIONS>]`

## Description

The `snyk cos scan start` command starts a new scan on a target. By default, the command returns immediately after starting the scan.

Use the `--wait` option to block until the scan finishes and print the report.

For a list of related commands see the [snyk cos](/developer-tools/snyk-cli/commands/cos.md) help, `snyk cos --help`.

## Exit codes

Possible exit codes and their meaning:

**0**: scan started\
**2**: failure, the target already has a running scan, the target is unreachable, or authentication failed\
**3**: failure, target ID not found

## Configure the Snyk CLI

You can use environment variables to configure the Snyk CLI and set variables for connecting with the Snyk API. For more information see [Configure the Snyk CLI](https://docs.snyk.io/snyk-cli/configure-the-snyk-cli).

## Debug

Use the `-d` option to output the debug logs.

## Options

### `--target-id=<TARGET_ID>`

**Required**. Specify the target to scan. The `<TARGET_ID>` must be a valid target ID.

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5
```

### `--wait`

Wait for the scan to complete and print the report. When set, the command blocks until the scan finishes or the `--timeout` value is reached.

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5 --wait
```

### `--timeout=<DURATION>`

Specify the maximum time to wait when `--wait` is set. Use the format `<VALUE><UNIT>`, where unit is `s` (seconds), `m` (minutes), or `h` (hours), for example, `30s`, `5m`, or `1h`.

Default: `30m`

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5 --wait --timeout=60m
```

### `--interval=<DURATION>`

Specify the polling interval when `--wait` is set. Use the format `<VALUE><UNIT>`, where unit is `s` (seconds), `m` (minutes), or `h` (hours), for example, `30s`, `5m`, or `1h`.

Default: `5s`

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5 --wait --interval=10s
```

### `--json`

Print the report on the console as a JSON data structure. Requires `--wait`.

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5 --wait --json
```

### `--output-file=<FILE_PATH>`

Write the JSON report to the specified file path. Requires `--wait` and `--json`.

Example:

```bash
$ snyk cos scan start --target-id=92b10f07ec07c7b1b73305181398ccf5 --wait --json --output-file=./report.json
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/developer-tools/snyk-cli/commands/cos-scan-start.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.