Skip to main content
Running vio with no arguments opens an interactive shell:
This is the CLI’s front door. Most of what you can do as a subcommand you can also do here, as a slash command, without retyping vio each time.
The shell needs a real terminal. If vio is started with its input piped or redirected — from a script, a CI job, or another program — it exits with vio needs an interactive terminal. Use the subcommands there instead; that is what they are for.

What you can type

Type a sentence and it goes to the Viorant Assistant. Start a line with / and it is a command instead:
Type / and the start of a name to pick from the matching commands. /help lists every command in the build you are running, with its arguments. In vio 1.0.6 that is: A slash command takes the same options as its subcommand, --json included. /deploy, for example, takes --target, --env-file, --name, --verbose-logs, --json and --show-run-key. Three commands have no slash form: vio run, vio run-key and vio update. Run them as subcommands. /clear, /exit, /quit, /session, /tier and /create exist only in the shell.

The Assistant

Anything you type that does not start with / goes to the Assistant: an agent loop that reads your Space, edits it, and runs vio for you. It runs on Viorant credits through the credits gateway, so every turn spends credits from your wallet, at the tier you set with /tier. See Credits.
The Assistant is on by default in vio 1.0.6. To go back to the earlier plan-and-approve Assistant, set VIORANT_FLAG_ASSISTANT_AGENT=0 in the environment before you start vio. The earlier one proposes a plan and waits for your approval before it writes anything.

What it can change

In your Space, the Assistant reads and lists files, and writes or edits them. It can also create prompt, skill and memory assets. A write lands at once, and the transcript shows the diff, so read it as it scrolls past. There is no approval step before a file is written. It stays inside the Space. It never reads or writes .vio/, which holds your keys and connector tokens, or .git/, or anything outside the Space. A request to do so is refused, and nothing from that path reaches the model. A turn stops after 12 rounds of tool calls.

What it runs for you

The Assistant runs read-only commands on its own: help, docs, validate, providers, connectors, whoami, status, list, show, runs and logs. A few forms stop being automatic, because they write a file, read credentials, or use a staged connector token: docs --refresh, any --fix, any --env-file, validate --check-tools and connectors tools. Those become cards too. Everything else becomes a command card. A card shows the command, why it matters and what you are approving:
  • Enter runs it.
  • Esc dismisses it.
Cards cover deploys, redeploys, connects, stops and the rest, so the Assistant can’t deploy, connect or stop anything unless you press Enter. A card for vio run, vio run-key or vio update has no slash form to run, so it is shown to copy into your own terminal, and Enter then means you did it (“Enter when done”).

The status line

A line under the composer shows where you are: the Space, whether agent.vio is valid (✓ or ✗), the deployment and its state, any pending connectors, and the last run. It refreshes about every 60 seconds, and straight after a deploy, redeploy, connect, stop, schedule, init or create. The Assistant sees the same line. Esc stops a turn that is still running. If you want an AI coding agent to drive vio, that works through the subcommands, not this shell. See Use vio with AI coding agents.

Sessions

Each shell run gets a session, written to ~/.viorant/sessions/. /session prints its id, working directory and start time, and vio --resume <session-id> reopens it.

Scripts and CI

The shell is for people. In a script, a CI job, or anything without a terminal, call the subcommands directly:
They are the automation surface, they are not going away, and they exit with stable codes you can branch on.