> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/cli/release.md).

# Command reference

Command reference doc for the Release CLI

The official CLI for Release (release.com)

## Options

| `--config <string>` | config file (default is $HOME/.release.yaml) |
| ------------------- | -------------------------------------------- |
| `--debug`           | enable debug logging                         |

## Related

* [release accounts](/cli/release/accounts.md) - Manage accounts
* [release ai](/cli/release/ai.md) - Work with ai
* [release apps](/cli/release/apps.md) - Manage apps
* [release auth](/cli/release/auth.md) - Manage authentication (login, logout, etc.)
* [release builds](/cli/release/builds.md) - Manage builds
* [release clusters](/cli/release/clusters.md) - Manage clusters
* [release datasets](/cli/release/datasets.md) - Manage datasets
* [release deploys](/cli/release/deploys.md) - Manage deploys
* [release development](/cli/release/development.md) - Work with remote development environments
* [release environments](/cli/release/environments.md) - Manage environments
* [release gitops](/cli/release/gitops.md) - Manage GitOps config
* [release instances](/cli/release/instances.md) - Manage instances


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/cli/release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.