VIORANT CLI

# DEPLOY AN AGENT. FROM YOUR TERMINAL.

vio is the Viorant CLI. It validates a [.vio](/vio) file, stands the agent up on [Viorant Cloud](/cloud), and hands you a URL.

The same deploy pipeline as the [Hub](/hub), without opening the Hub.

[Install vio](#install)[Documentation](https://docs.viorant.ai/cli/install)

$ vio login

$ vio validate agent.vio

$ vio deploy agent.vio --target viorant_cloud --env-file creds.env

## INSTALL

macOS and Linux:

curl -fsSL https://dl.viorant.ai/cli/install.sh | sh

vio needs Node 22. It installs to your home directory without sudo. Run the same command again to upgrade.

Windows: download the release file from dl.viorant.ai and check its sha256 checksum by hand.

## THREE COMMANDS TO A RUNNING AGENT

-

### 01 Sign in

vio login

Google sign-in in your browser. One owner-only credential file on your machine.

-

### 02 Validate

vio validate agent.vio

Local and offline. No account needed. An invalid file fails with the exact field that is wrong.

-

### 03 Deploy

vio deploy agent.vio --target viorant_cloud --env-file creds.env

You get a URL and a run key, shown once. Your provider key is sealed on your machine before it leaves it.

Then call it:

curl -sS -X POST https://<service>.a.run.app/run -H "Authorization: Bearer <run key>" -H "Content-Type: application/json" -d '{"task":"..."}'

## AFTER DEPLOY

- vio status : your plan, credit balance, and how many agents you can still deploy.

- vio list and vio show <id> : your deployments and their state.

- vio runs <id> : recent runs of a deployed agent.

- vio logs <id> : recent logs of a deployed agent, with terminal control stripped and common secrets redacted.

- vio redeploy <id> : replace a running agent in place. The URL stays the same.

- vio connect <id> : authorise or re-authorise the agent's connectors in your browser. No redeploy.

- vio stop <id> : stop the agent and revoke its credentials.

## WHAT TEAMS USE IT FOR

### Ship from CI

vio validate --json gates a pull request. A merge redeploys the agent in place.

### Keep agents in git

A .vio file is reviewable text with a canonical digest. Diff it, review it, and deploy exactly what was merged.

### Operate without a desktop

Check runs and logs, re-authorise connectors, and stop agents from a server or an SSH session.

### Let your coding agent build it (coming)

Claude Code or Codex writes the .vio file, validates it, and deploys it with vio. You approve the sign-in and the deploy.

## BUILT TO BE CHECKED

### Signed releases

Every release is signed with Sigstore from the Viorant release workflow and recorded in the public Rekor transparency log.

### Verified on install

The installer always checks the checksum, and checks the signature whenever cosign is installed.

### No provider keys stored

Provider keys are sealed and sent to your deployment. Connector tokens never touch disk.

### Run keys shown once

A run key is printed once and never written to disk or to the session transcript.

Deploys run through [Helix](/helix), the same engine the Hub uses.

## COMING NEXT

- Deploy on your Viorant credits, without a provider key.

- Scaffold a working agent with one command.

- vio as a coding agent: the same terminal, with a model behind it, metered on your credits.

## QUESTIONS

### Do I need the Hub?

No. The Hub and vio deploy through the same pipeline. Use either.

### Does validating cost anything?

No. Validation runs offline with no account. Deployed agents count against your plan's agent limit.

### How do I upgrade?

Run the install command again. vio --version shows what you have.

## ONE DEFINITION. TWO WAYS TO SHIP IT.

Author in the Hub or in your editor. Deploy from either.

[Install vio](#install)[Download the Hub](/download)