CLI reference

The vops CLI is the complete human surface for provider research, infrastructure, hosts, applications and local agent governance. Commands are grouped by the object they operate:

vops <topic> <command> [arguments] [flags]

Use built-in help for the exact flags in the installed version:

vops --help
vops host --help
vops host status --help

Topics

Topic	What it does	Reference
providers / compare	Capabilities, locations, plans, prices and availability.	Providers and servers
servers	Plan, create, list, inspect and delete provider resources.	Providers and servers
firewall / vnet	Provider-native firewalls and private networks.	Providers and servers
ssh-key / ssh	Local key references, provider registration and direct sessions.	Hosts and security
host / host-firewall	Inventory, health, updates, hardening and host firewall.	Hosts and security
spec / catalog	Generate and validate flui.yaml; inspect deployable entries.	Applications, ingress and backups
build / deploy	CI image production and immutable deployment plans.	Applications, ingress and backups
app / ingress	Application lifecycle, logs, exposure, TLS and access gates.	Applications, ingress and backups
backup	Configure, run, inspect, restore and remove host backups.	Applications, ingress and backups
bench / watch	Performance measurements and opt-in hosted notifications.	Operations and local state
config / keyring / ui	Credentials, local vault lifecycle and dashboard.	Operations and local state
agent / capability / knowledge / mcp	Controlled development-agent setup and human governance.	Agent control

Human and JSON output

Commands that participate in agent-first workflows also expose --json. The machine form uses structured data, stable error codes, warnings and suggested next actions. Human output is optimized for terminal review.

Do not parse colorized prose in automation. Use --json and check the process exit code.

Confirmation conventions

Common patterns are:

• --dry-run renders or validates without changing remote state;
• omitting --yes prints a plan or approval requirement;
• --yes executes the reviewed mutation;
• --force, --purge and similar command-specific flags enlarge the effect.

Not every command implements every flag. Check the command’s help before assuming a shared convention applies.

Profiles

The active profile is selected with VOPS_PROFILE. Each profile has isolated credentials, keys, inventory and operational state under ~/.config/vops/profiles/<name>/. With no override, vops uses the default profile.