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

# Devolutions CLI

Devolutions CLI keeps your secrets in a Devolutions vault and hands them to a command only while it runs, for developers, CI pipelines, and AI agents.

**Commit the reference, never the secret.**

Scripts, `.env` files, CI pipelines, and AI coding agents all need passwords, API keys, and tokens. Most of the time those values end up pasted into files, environment variables, or chat transcripts. Devolutions CLI keeps them in your Devolutions vault and resolves them only when a command starts, so your files hold a `devo://` reference instead of the value.

Devolutions CLI is one command, `devo`, for Windows, macOS, and Linux. It works with Devolutions Cloud, Devolutions Server, and local Devolutions Remote Desktop Manager profiles, with the same commands for all three.

## What do you want to do?

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Take secrets out of my code</strong></td><td>Replace passwords in scripts and <code>.env</code> files with references, and run your commands with the real values.</td><td><a href="/cli/guides/secrets/run-with-secrets.md">Run a command with its secrets</a></td></tr><tr><td><strong>Give an AI agent a credential</strong></td><td>Let Claude Code, GitHub Copilot, or another agent use a credential without the value reaching its transcript.</td><td><a href="/cli/guides/ai-agents/run-an-agent.md">Give an agent a credential without exposing it</a></td></tr><tr><td><strong>Use secrets in a CI pipeline</strong></td><td>Sign in without a prompt, read JSON output, and install Devolutions CLI on your build agents from one archive.</td><td><a href="/cli/for-devops-and-administrators/automate/ci-sign-in.md">Sign in from a CI pipeline</a></td></tr><tr><td><strong>Manage my workspace from a terminal</strong></td><td>Work with vaults, entries, users, groups, and access in Devolutions Cloud, Devolutions Server, or a local profile.</td><td><a href="/cli/for-devops-and-administrators/manage/vaults-and-entries.md">Manage vaults and entries</a></td></tr></tbody></table>

## New to Devolutions CLI?

{% content-ref url="/pages/dhdbgjsWG2lYi38D14cB" %}
[Quick start](/cli/quick-start.md)
{% endcontent-ref %}

Five minutes from installation to a command that runs with a secret from your vault.

{% content-ref url="/pages/xRnHiB8hbPTTGTJISqwd" %}
[How Devolutions CLI works](/cli/guides/understand/how-it-works.md)
{% endcontent-ref %}

Contexts, workspaces, and `devo://` references: the three ideas behind every Devolutions CLI command.

{% content-ref url="/pages/F7QvvDfXlLfAE7KfwZMg" %}
[What stays hidden, and what doesn't](/cli/guides/understand/security-model.md)
{% endcontent-ref %}

Which commands keep a secret hidden, which ones hand it over, and what Devolutions CLI can't protect you from.

Have a quick question, like *"Do I need Devolutions Remote Desktop Manager installed?"* Check the [frequently asked questions](/cli/help/troubleshooting/faq.md).

## Something isn't working?

Start with [Troubleshooting](/cli/help/troubleshooting.md). It's organized by what you see, like *"A secret reference doesn't resolve"* or *"Sign-in fails"*.


---

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