How Devolutions CLI works
Devolutions CLI doesn't store your secrets. It points at them. Your scripts, .env files and agent instructions hold a devo:// reference, and Devolutions CLI fetches the value from your workspace only at the moment a command needs it. Understanding this one idea explains almost everything else: what you can safely commit, why you sign in once, and which commands keep a secret hidden.
Four building blocks
Workspace
Where your secrets live: Devolutions Cloud, Devolutions Server, or a local Devolutions Remote Desktop Manager profile. Inside it, secrets sit in fields of entries, grouped in vaults.
The password field of the Production database entry, in the Operations vault.
Context
A saved connection to one workspace, with a name you choose. You create it once with devo login, and every command after that uses the current context.
my-cloud, work-server, my-local
Reference
The address of one field, starting with devo://. It says where the secret is, never what it is.
devo://<workspace>/<vault>/<entry>/password
Command
The program that needs the secret. devo secret run resolves the references, gives the values to that program only, and starts it.
A deployment script, a database client, an AI agent.
What this means for you
References are safe to share. A reference contains names or IDs, not a value. You can commit it, paste it in a ticket, or give it to an AI agent. Without access to the vault, it opens nothing. See Secret reference syntax.
You sign in once, then work. devo login saves the context and makes it current, so later commands don't ask again. To use another workspace for a single command, add --context <name>. See Switch between workspaces.
The same commands work everywhere. Reading a secret or running a command looks the same on Devolutions Cloud, Devolutions Server, and a local profile. When a workspace can't do something, the command says so instead of failing silently. See Compare workspace types.
A secret reaches only the command you start. devo secret run puts the values in the environment of that one program, not in your shell. Devolutions CLI refuses references written as command arguments, and hides resolved values in what the program prints. See Run a command with its secrets.
Some commands hand the value over on purpose. Reading a secret to the terminal, filling a template file, loading secrets in your current shell, or letting an AI client read an entry gives you, or the model, the actual value. Pick the command that matches how much you want to expose. See What stays hidden, and what doesn't.
The background process
To stay fast, devo starts a background process the first time a command needs your workspace, and reuses it afterward. It's the same devo file running in the background, under your user account, and it talks to devo over a local channel on your computer. You don't need to install a service or start anything yourself.
If you'd rather control it, the --daemon option accepts auto (the default: start it when needed), require (use one that's already running), or never. The devo daemon commands show its status, stop it, or restart it. See The background process won't start.
Last updated
Was this helpful?