tovio: command not found, or the wrong version runs

PATH problems, duplicate installs, and the version flag.

Written By Dustin

Last updated 16 minutes ago

Command not found

The binary is not on your PATH. If you built from source it is at target/release/tovio — copy it somewhere on your PATH or add that directory.

Check what your shell finds:

which tovio      # or: where toviotovio --version

Asking for the version

It is tovio --version — a flag, not a subcommand. tovio version exits with unrecognized subcommand (a usage error, exit class 2), which reads like a broken install but is not one. tovio -V works too.

The wrong version runs

You have more than one installed. Common causes: a built binary and a packaged one, or a copy in a project directory shadowing the real one. List every match on your PATH, not just the first:

which -a tovio    # macOS, Linuxwhere tovio       # Windows — lists every match already

Remove the one you do not want, or fix the PATH order.

It works in the terminal but not in the editor

Both extensions shell out to tovio. On macOS a GUI-launched editor often does not inherit your shell PATH. Open a terminal inside the editor and run tovio --version: if that fails, so will the extension. Launch the editor from a terminal, or set the binary path in extension settings.

A command exists but the index does not show it

The everyday help index is deliberately short. Team and Advanced commands are still runnable — they are just not listed by default.

tovio help --alltovio help <command>

After an upgrade

Regenerate shell completions — they are generated from the command surface at the version you ran, so stale completions will offer commands your binary no longer has.

tovio completions <shell>

Reporting it

The version string and your OS are enough. No paths.