> 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/getting-started.md).

# Getting started

Create and deploy [Release](https://releasehub.com/) environments, stream logs, and more from the command line.

[Download & install](/cli/installation.md)

[Usage docs](/cli/release.md)

## Quickstart

To install via [Homebrew](https://brew.sh/):

```
brew install releasehub-com/tap/release-cli
```

To allow the CLI access to your Release account, run:

```
release auth login
```

This will open a browser window and you can complete the login via the Release web UI.

If your browser doesn’t open automatically, visit the URL the `release auth login` command provides you with to complete the login.

Once you have installed the CLI through Homebrew, you should have access to shell completions automatically. If you don't, take a look at [how to install shell completions manually](/cli/installation.md#shell-completions).

Find alternative installation methods in our [installation guide](/cli/installation.md). The Release CLI is supported on macOS, Windows, and Linux.

## Usage

See the [command reference](/cli/release.md) documentation for available commands and usage examples.

To get started quickly, try our [CLI usage example](/cli/cli-usage-example.md).

You can also read about [the CLI configuration](/cli/configuration.md).


---

# 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/getting-started.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.