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

# release environments

Command reference doc for the Release CLI

Manage environments

## Options inherited from parent commands

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

## Related

* [release](/cli/release.md) - The official CLI for Release (release.com)
* [release environments config-get](/cli/release/environments/config-get.md) - Get an environment's current config and prints it to standard output
* [release environments config-set](/cli/release/environments/config-set.md) - Update an environment's config with YAML given on standard input
* [release environments create](/cli/release/environments/create.md) - Create an ephemeral environment and automatically deploy it (by default)
* [release environments delete](/cli/release/environments/delete.md) - Delete an ephemeral environment
* [release environments get](/cli/release/environments/get.md) - Get an environment
* [release environments list](/cli/release/environments/list.md) - List environments
* [release environments pause](/cli/release/environments/pause.md) - Pause a running environment
* [release environments resume](/cli/release/environments/resume.md) - Resume a paused environment
* [release environments vars-get](/cli/release/environments/vars-get.md) - Get an environment's current environment variables and prints them to standard output


---

# 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/environments.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.