Workspace and account

Command	Purpose
vatio init [SLUG] [--name NAME]	Create or use the remote workspace and write a starter manifest in the current directory
vatio login [--base-url URL]	Authorize this machine through the browser
vatio logout	Remove the saved token
vatio doctor	Show Node version, config location, workspace, and token presence
vatio version	Show CLI and Node versions
vatio docs [--save [PATH]]	Fetch the docs; print them or save to vatio-docs.md / PATH
vatio config show / get KEY / set KEY VALUE / unset KEY	Manage local base_url and token settings

init writes vatio.yml in the current directory and asks for no account: you can write the whole agent without signing up. Identity is what vatio push needs, because it is the first thing that makes something run on a server, and there the CLI asks for an email and mails you a link. Every other command finds the nearest vatio.yml at or above the current directory and reads workspace from it — there is no --workspace flag and no VATIO_WORKSPACE override.

Reach for doctor before anything else when a command cannot find the workspace or the token: it prints all four things that decide that, and prints no secrets, so it is the safe one to paste into an issue.

Issues

Command	Purpose
vatio issue "message" / --file PATH / --template / --no-source	Send a report or fetch the report template; run from a workspace it attaches the directory, --no-source does not
vatio issue list / show ID / comment ID "reply"	Read and reply to your support threads

Issue and comment commands send immediately. Review the text before running them, and see Troubleshooting for what to include.