> 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/help/troubleshooting/faq.md).

# Frequently asked questions

Short answers to the questions people ask most about Devolutions CLI, with a link to the detailed page for each one.

Quick answers to the most common questions. Each one links to the page with the details.

## About Devolutions CLI

<details>

<summary>Do I need Devolutions Remote Desktop Manager installed?</summary>

No. Devolutions CLI is a self-contained `devo` program that includes what it needs. With Devolutions Cloud or Devolutions Server, it talks to the workspace directly. With a local Devolutions Remote Desktop Manager profile, it reads the profile folder itself, so it only needs the folder, not the application. See [Use a local Devolutions Remote Desktop Manager profile](/cli/guides/connect/local-profile.md).

</details>

<details>

<summary>Which platforms does it run on?</summary>

Windows, macOS, and Linux, on x64 and Arm64 processors. Each platform gets its own archive, with `devo.exe` on Windows and `devo` on macOS and Linux. See [Install Devolutions CLI](/cli/reference/installation.md).

</details>

<details>

<summary>Which workspaces does it work with?</summary>

Devolutions Cloud, Devolutions Server, and local Devolutions Remote Desktop Manager profiles, with the same commands. Some tasks exist on one workspace type only. When the selected workspace can't do something, the command says so. See [Compare workspace types](/cli/guides/understand/workspace-types.md).

</details>

## Secrets and security

<details>

<summary>Does Devolutions CLI send my secrets anywhere?</summary>

Only where you tell it to. `devo secret run` reads a secret from your workspace and puts it in the environment of the one command you start, not in your shell. `devo` and its background process talk over a local channel on your computer, not over the network. The telemetry preference is off unless you turn it on with `devo config telemetry set`. See [What stays hidden, and what doesn't](/cli/guides/understand/security-model.md) and [What data Devolutions CLI sends](/cli/guides/understand/privacy.md).

</details>

<details>

<summary>Can an AI agent see my passwords?</summary>

It depends on how the agent gets them. When the agent runs `devo secret run`, the value goes to the command it starts, and Devolutions CLI replaces it with `<concealed by Devolutions>` in what that command prints, so it stays out of the transcript. When the agent is connected with `devo mcp`, it can ask for a secret value and receive it. Choose the approach accordingly, and limit the MCP tools. See [Work with AI agents](/cli/guides/ai-agents.md) and [Limit what an agent can do](/cli/guides/ai-agents/limit-tools.md).

</details>

<details>

<summary>Is it safe to commit a devo:// reference?</summary>

Yes. A reference holds names or IDs, never the value. Without access to the vault, it opens nothing. See [Secret reference syntax](/cli/reference/secret-references.md).

</details>

## Using Devolutions CLI

<details>

<summary>Can I use several workspaces?</summary>

Yes. Sign in to each one with `devo login` and a context name of your choice. `devo context use <context-name>` changes the current one, and `--context <context-name>` picks another one for a single command. See [Switch between workspaces](/cli/guides/connect/switch-workspaces.md).

</details>

<details>

<summary>Is there a JSON output?</summary>

Yes. Add `--output json`, or its shortcut `--json`, to any command. `--output yaml` works too. Errors come in the same format, with a code and a message. See [Read results as JSON](/cli/for-devops-and-administrators/automate/json-output.md).

</details>

<details>

<summary>Why does a command refuse to change anything?</summary>

Commands that change your workspace need `--yes`. Without it, they stop with `confirmationRequired` and change nothing, so a script or an agent can't make a change by accident. See [Run without prompts](/cli/for-devops-and-administrators/automate/non-interactive.md).

</details>

<details>

<summary>What is the background process I see running?</summary>

It's the same `devo` file, running under your account to keep your workspace connection ready. The first command that needs it starts it, and it stops by itself after 60 minutes without use. `devo daemon status` shows it, and `devo daemon stop` stops it. See [The background process won't start](/cli/help/troubleshooting/daemon-wont-start.md).

</details>

<details>

<summary>How do I sign out?</summary>

Run `devo logout <context-name>`. It clears the stored sign-in of a Devolutions Cloud or Devolutions Server context and keeps the context, so you can sign in again later with `devo login`. To remove the context as well, run `devo context delete <context-name> --yes`. A local profile has no sign-in to clear. See [Switch between workspaces](/cli/guides/connect/switch-workspaces.md).

</details>

<details>

<summary>Can I use it in a CI pipeline?</summary>

Yes. Sign in with an application key (Devolutions Cloud) or an API key (Devolutions Server) read from an environment variable or a file, and add `--non-interactive` so a missing value fails instead of waiting for an answer. See [Sign in from a CI pipeline](/cli/for-devops-and-administrators/automate/ci-sign-in.md).

</details>

## Getting help

<details>

<summary>What do I send to support?</summary>

The output of `devo doctor`, the command you ran, and the full error, never a secret value. See [Collect diagnostics for support](/cli/help/troubleshooting/collect-diagnostics.md).

</details>

## Still stuck?

* Browse [Troubleshooting](/cli/help/troubleshooting.md), organized by what you see.
* Check the [glossary](/cli/reference/glossary.md) if a term is unclear.


---

# 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/help/troubleshooting/faq.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.