Configure the JetBrains plugin

Where the settings are, and where they differ from VS Code.

Written By Dustin

Last updated About 3 hours ago

Settings → Tools → TOVIO. The settings are application-level, not per-project, so they follow you across every project in that IDE.

SettingDefaultWhat it does
Executable pathtovioHow the plugin finds the CLI. The default resolves it on the PATH the IDE sees.
Status baronThe lane / change / counts widget.
DecorationsonFile decoration in the project view.
Refresh debounce300 msClamped to 50–5000, the same bounds as the VS Code setting.
Rationale hoveronThe owning change and recorded rationale on hover.
Token warningsonWarn when an agent capability token is expiring or expired.

Where it differs from VS Code

The plugin deliberately mirrors the extension's settings, with two absences: there is no inline-blame toggle and no history limit. If you rely on either in VS Code, expect them not to be there.

In the other direction, the JetBrains side gets things the extension does not have: a checkout provider under "Get from Version Control", the unified VCS Log graph, a pre-commit conflict gate, and Lock/Unlock in the file context menus.

Which IDEs

One artifact, built against the IntelliJ Community platform and depending only on the platform and VCS modules, so it loads across IDEA, WebStorm, PyCharm, GoLand, and RustRover. The minimum platform is 2024.2 (build 242), and the upper bound is deliberately left open rather than pinned to a version range.

Be precise about what that is worth: the plugin verifier runs against IntelliJ IDEA Community only, at the oldest supported build and the current stable one. The other IDEs are supported by construction — same platform base, same module dependencies — not by a verification run. If you hit something IDE-specific in GoLand or RustRover, that is exactly the report worth filing.

When something looks wrong

Open the Output tab of the TOVIO tool window. Every CLI invocation the plugin makes is logged there with its result, which turns "the panel is empty" into a specific failing command.