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

# Install Devolutions CLI

Supported platforms and architectures of Devolutions CLI, what it needs, where its configuration lives, and how to update and uninstall it.

Devolutions CLI is a single command, `devo`, published for each platform as a self-contained archive (`.zip` or `.tar.gz`). There's no installer to run and nothing else to install.

## Supported platforms

<table><thead><tr><th width="200">PLATFORM</th><th width="200">ARCHITECTURES</th><th>COMMAND FILE</th></tr></thead><tbody><tr><td>Windows</td><td>x64, Arm64</td><td><code>devo.exe</code></td></tr><tr><td>macOS</td><td>x64, Arm64</td><td><code>devo</code></td></tr><tr><td>Linux</td><td>x64, Arm64</td><td><code>devo</code></td></tr></tbody></table>

## What you need

* **Nothing else on your computer.** Devolutions CLI is compiled ahead of time and includes everything it runs on, so you don't need to install .NET or Devolutions Remote Desktop Manager. It reads local Devolutions Remote Desktop Manager profiles on its own.
* **A workspace to connect to**: an account on Devolutions Cloud or Devolutions Server, or a local Devolutions Remote Desktop Manager profile. See [Connect to your workspaces](/cli/guides/connect.md).

## Install

1. Download the package for your platform and architecture.
2. Extract the whole archive to a folder of its own, for example a `devo` folder in your tools folder. Keep the extracted files together: `devo` (`devo.exe` on Windows) may need the other files of the archive next to it.
3. Add that folder to your `PATH`.
4. Open a new terminal and check that Devolutions CLI answers:

```bash
devo --version
```

Next, sign in to your workspace: see [Quick start](/cli/quick-start.md). To install Devolutions CLI on build agents, see [Install Devolutions CLI on build agents](/cli/for-devops-and-administrators/automate/install-on-runners.md).

## Where the configuration lives

Devolutions CLI keeps its configuration, such as your contexts, in a folder of your user profile, separate from the folder where you extracted the program:

<table><thead><tr><th width="250">FOLDER</th><th>WHAT'S IN IT</th></tr></thead><tbody><tr><td><code>Devolutions/CLI</code>, in your user's local application data folder</td><td>Your contexts and the other Devolutions CLI settings. If the local application data folder isn't available, Devolutions CLI uses <code>.devolutions/cli</code> in your home folder. Set <code>DEVO_CLI_CONFIG_HOME</code> to use another folder.</td></tr><tr><td><code>rdm</code>, inside that folder</td><td>The default local Devolutions Remote Desktop Manager profile. Set <code>RDM_CONFIG_PATH</code> to use another profile folder. <code>devo config path</code> prints the folder in use.</td></tr></tbody></table>

See [Environment variables](/cli/reference/environment-variables.md) and [What data Devolutions CLI sends](/cli/guides/understand/privacy.md).

## Update

Devolutions CLI has no update command. To update it, replace the contents of the folder where you extracted it with the new archive. Your contexts and settings are kept, because they're stored in a separate folder.

Stop the background process first, so the old version isn't running while you replace the files:

```bash
devo daemon stop --wait
```

## Uninstall

1. Sign out of each Devolutions Cloud and Devolutions Server context, to clear its stored sign-in:

   ```bash
   devo logout <context-name>
   ```
2. If you registered Devolutions CLI with SecretSpec, remove the claim:

   ```bash
   devo secretspec unregister
   ```
3. Stop the background process:

   ```bash
   devo daemon stop --wait
   ```
4. Delete the folder where you extracted Devolutions CLI, and remove it from your `PATH`.
5. To remove your contexts and settings too, delete the Devolutions CLI configuration folder. If your local profile is in its `rdm` folder, back it up first: deleting the folder deletes that profile and its workspaces.


---

# 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.devolutions.net/cli/reference/installation.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.