Skip to main content
A .vio file is a portable definition of a whole agent — prompt, model, skills, connectors and memory — in one YAML file. Everything the agent is made of is inside the file, so you can deploy a .vio someone sent you without any other assets.

​
Validate

Validation is local: no sign-in and no network. A valid file prints a summary of what it contains. An invalid one exits 1 and names each field that’s wrong. Point vio at a folder and it looks for the .vio inside it (one level deep, not subfolders):
One match is used. Several is an error that lists them; none is a distinct “no .vio bundle found” error. For scripts and CI, print one JSON result:

​
Digest

Prints the deployment digest — the value a deployment records, and the one vio show and the Hub compare against. --content prints the whole-file content digest instead, and --json prints both.
Each part of a .vio carries its own digest in the manifest. vio validate checks the structure of the file, not those per-part digests. A file that was hand-edited after it was exported can pass validation and still be refused at deploy. Re-export it from the Hub rather than editing it by hand.

​
Deploying a .vio you were given

1

Put it in a folder

2

Validate it

3

Deploy it

Follow Deploy an agent. You provide the model provider key; the file never contains one.