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

# Global options

Options that every Devolutions CLI command accepts: output format, workspace selection, background process, prompts, and notices, with defaults and conflicts.

These options work with every `devo` command, before or after the command name. For example, `devo --json context list` and `devo context list --json` do the same thing.

## Output

<table><thead><tr><th width="250">OPTION</th><th width="120">DEFAULT</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>--output &#x3C;format></code></td><td><code>text</code></td><td>Output format: <code>text</code>, <code>json</code>, or <code>yaml</code>. JSON and YAML return the result in an envelope that scripts can read. See <a href="/cli/for-devops-and-administrators/automate/json-output.md">Read results as JSON</a>.</td></tr><tr><td><code>--json</code></td><td>Off</td><td>Same as <code>--output json</code>.</td></tr><tr><td><code>--yaml</code></td><td>Off</td><td>Same as <code>--output yaml</code>.</td></tr><tr><td><code>--quiet</code></td><td>Off</td><td>Hides the notices that aren't part of the result, such as a message saying the background process was started.</td></tr><tr><td><code>--verbose</code></td><td>Off</td><td>Writes those notices to the error output, even with <code>--output json</code> or <code>--output yaml</code>. Without <code>--verbose</code>, they only appear in text output.</td></tr></tbody></table>

## Workspace selection

By default, a command uses the current context, the one you last signed in to or selected with `devo context use`. These options pick another workspace for one command only. See [Switch between workspaces](/cli/guides/connect/switch-workspaces.md).

<table><thead><tr><th width="250">OPTION</th><th width="120">DEFAULT</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>--context &#x3C;name></code></td><td>Current context</td><td>Uses the context <code>&#x3C;name></code>: a local Devolutions Remote Desktop Manager profile, or a Devolutions Cloud or Devolutions Server sign-in. Takes priority over the <code>DEVO_CONTEXT</code> environment variable.</td></tr><tr><td><code>--source &#x3C;source></code></td><td></td><td>Uses a workspace type: <code>sqlite</code> for the local profile, <code>cloud</code> or <code>cloud:&#x3C;context></code> for Devolutions Cloud, <code>server</code> or <code>server:&#x3C;context></code> for Devolutions Server. Takes priority over <code>--context</code> and the <code>DEVO_RDM_SOURCE</code> environment variable.</td></tr></tbody></table>

## Background process

Most commands that read your workspace go through a background process that `devo` starts on its own. See [How Devolutions CLI works](/cli/guides/understand/how-it-works.md#the-background-process).

<table><thead><tr><th width="250">OPTION</th><th width="120">DEFAULT</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>--daemon &#x3C;policy></code></td><td><code>auto</code></td><td><code>auto</code> starts the background process when it's needed. <code>require</code> uses one that's already running and never starts one. <code>never</code> fails instead of contacting it. Takes priority over the <code>DEVO_DAEMON_MODE</code> environment variable.</td></tr><tr><td><code>--no-daemon-autostart</code></td><td>Off</td><td>Doesn't start the background process automatically.</td></tr></tbody></table>

## Prompts

<table><thead><tr><th width="250">OPTION</th><th width="120">DEFAULT</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>--non-interactive</code></td><td>Off</td><td>Fails instead of asking for missing input. Also on when the <code>DEVO_NON_INTERACTIVE</code> environment variable is turned on (any value except <code>0</code>, <code>false</code>, or <code>no</code>), or when the standard input is redirected, for example in a pipeline.</td></tr><tr><td><code>--answer &#x3C;answer></code></td><td></td><td>Answers a prompt in advance. Repeat for several prompts: answers are used in order. For a choice, give the label of the option or its number, starting at <code>0</code>. Answers from the <code>DEVO_PROMPT_ANSWERS</code> environment variable come after these.</td></tr></tbody></table>

See [Run without prompts](/cli/for-devops-and-administrators/automate/non-interactive.md).

## Help and version

<table><thead><tr><th width="250">OPTION</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>--help</code></td><td>Shows the help of the command: its description, subcommands, arguments, and options. Works at every level, such as <code>devo --help</code> or <code>devo secret run --help</code>.</td></tr><tr><td><code>--version</code></td><td>Shows the version of Devolutions CLI. Use it with <code>devo</code> alone.</td></tr></tbody></table>

## Options that can't be combined

These combinations stop the command before it runs, with the error code `conflictingOptions` and exit code `2`:

<table><thead><tr><th width="300">COMBINATION</th><th>MESSAGE</th></tr></thead><tbody><tr><td><code>--json</code> with <code>--yaml</code></td><td>"Use only one output selector: --json, --yaml, or --output."</td></tr><tr><td><code>--json</code> with <code>--output text</code> or <code>--output yaml</code></td><td>"Use either --json or --output with a matching format, not both."</td></tr><tr><td><code>--yaml</code> with <code>--output text</code> or <code>--output json</code></td><td>"Use either --yaml or --output with a matching format, not both."</td></tr><tr><td><code>--quiet</code> with <code>--verbose</code></td><td>"Use either --quiet or --verbose, not both."</td></tr></tbody></table>

An unknown `--source` value fails with the code `invalidSource` and exit code `2`. An unknown `--output` or `--daemon` value is rejected like any other invalid argument, with exit code `2`. See [Exit codes and errors](/cli/reference/exit-codes-and-errors.md).


---

# 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/global-options.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.