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

# Connecting to a Cluster

Connecting to a Cluster

See PUT Clusters for general information about the available clusters.

## Configure the command-line tool

You can check what cluster the PUT command-line tool (CLI) is currently targeting by running the following command:

```
put config get
```

Use put config set command to target a particular cluster. 

After setting a cluster target, any future subcommands will send/receive information from that cluster.

For example to target the Devnet cluster, run:

```
put config set --url https://rpc.putdev.com:8889
```

## Ensure Versions Match

Though not strictly necessary, the CLI will generally work best when its version matches the software version running on the cluster. 

To get the locally-installed CLI version, run:

```
put --version
```

To get the cluster version, run:

```
put cluster-version
```

Ensure the local CLI version is greater than or equal to the cluster version.


---

# 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.put.com/cli/connecting-to-a-cluster.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.