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

# release clusters shell

Command reference doc for the Release CLI

Starts a local shell with the given cluster's Kubernetes and AWS access credentials configured

## Description

Starts a local shell with the following environment variables set:

* `KUBECONFIG` set to a temporary file containg the cluster's Kubernetes config
* `AWS_ACCESS_KEY_ID` and `AWS_SECRET_KEY` set to credentials with access to the AWS account

This allows you to execute any locally installed command that respects those variables such as the `aws` CLI, kubectl, k9s, and many others.

This runs an an instance of your default shell respecting your `$SHELL` variable, falling back to `bash` if it's not set.

The temporary Kubeconfig file and environment variables will be cleaned up when you exit the shell.

Tip: Configure your shell to display the current Kubernetes cluster and AWS details in your prompt to make it clear which cluster/AWS account you're currently accessing.

```
release clusters shell [flags]
```

## Examples

```

Start a shell for the default cluster:
> release clusters shell

Start a shell for a specific cluster:
> release clusters shell --cluster CLUSTER-NAME-OR-ID

Start a shell configured for a given app environment's namespace:
> release clusters shell --app APP-NAME-OR-ID --environment ENVIRONMENT-HANDLE-OR-ID
```

## Options

| `--account <string>`     | Account name or ID (default: $RELEASE\_ACCOUNT or "account" in config file) |
| ------------------------ | --------------------------------------------------------------------------- |
| `--app <string>`         | App name or ID (default: $RELEASE\_APP or "app" in config file)             |
| `--cluster <string>`     | Cluster context or ID                                                       |
| `--environment <string>` | Environment handle or ID                                                    |

## Options inherited from parent commands

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

## Related

* [release clusters](/cli/release/clusters.md) - Manage clusters


---

# 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/clusters/shell.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.