Ship from CI
vio validate --json gates a pull request. A merge redeploys the agent in place.
VIORANT CLI
DEPLOY AN AGENT.
FROM YOUR TERMINAL.
vio is the Viorant CLI. It turns a folder into a .vio Space, deploys it to Viorant Cloud, and hands you a URL.
The same deploy pipeline as the Hub, without opening the Hub.
INSTALL
macOS and Linux:
curl -fsSL https://dl.viorant.ai/cli/install.sh | shvio 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 loginGoogle sign-in in your browser. One owner-only credential file on your machine.
02 Initialize
vio initTurns the folder into a Viorant Space: agent.vio and its files, ready to edit. Works offline, no account needed.
03 Deploy
vio deploy agent.vio --target viorant_cloudYou get a URL and a run key, shown once. Runs on your Viorant credits, no provider key required.
Between init and deploy, edit agent.vio yourself, or point Claude Code or Codex at the Space; vio init writes VIO-AGENTS.md to tell it how.
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":"..."}'To give the agent typed decisions mid-run, add the Jev MCP server: vio docs agents prints the recipe.
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.vio schedule <id> --every 1d --at 09:00: run the agent on a repeating schedule, in Viorant Cloud.
WHAT TEAMS
USE IT FOR
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
vio init writes a VIO-AGENTS.md so Claude Code or Codex can read what a Space needs and build agent.vio for you. Deploys still run under that agent's own permission model.
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
On macOS and Linux, the installer verifies the release signature itself, no extra tools needed. Install cosign for an independent check. On Windows, verify the sha256 checksum by hand.
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, the same engine the Hub uses.
COMING
NEXT
- 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.
Do I need my own provider key?
No. vio deploy runs on your Viorant credits by default. Pass --env-file only if you want to bring your own key.
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.