Editors, desktop & the shell
TOVIO where you already work. Status differs per surface, and each article says which.
- Install the VS Code extensionBuild it, install it, and point it at the CLI.
- What the VS Code extension gives youThe views and actions worth knowing about.
- Install the JetBrains pluginSetup, the feature set, and current limitations.
- TOVIO Desktop: what it does todayThe scope of the pre-release desktop app, honestly.
- Keep TOVIO up to dateWhat updating looks like today, and what the app does and does not do on its own.
- Show TOVIO state in your shell promptstatus --prompt, and how to wire it in safely.
- Use TOVIO from a scriptThe output contracts you can rely on.
- Present a token as a Git credentialgit-credential-tovio.
- Editor troubleshootingThe failures that account for most reports.
- Turn on shell completionsTab completion for bash, zsh, fish, PowerShell, and Elvish.
- Configure the VS Code extensionEvery setting, what it defaults to, and what it costs.
- Configure the JetBrains pluginWhere the settings are, and where they differ from VS Code.
- Desktop, dashboard, editor, or CLI?Four surfaces, and what each one can actually reach.
- Handle TOVIO errors in a scriptThe structured error shape, and how to branch on it correctly.
- What the editor and desktop surfaces sendThe short answer is: nothing, unless you click.