Install the JetBrains plugin
Setup, the feature set, and current limitations.
Written By Dustin
Last updated 15 minutes ago
The plugin is not on the JetBrains Marketplace yet, so installing means building it from a clone of the TOVIO repository:
git clone https://github.com/Tovio-VCS/tovio.gitcd tovio/packages/tovio-jetbrains-plugin./gradlew buildPluginThen Settings → Plugins → ⚙ → Install Plugin from Disk… and pick the zip from build/distributions/.
It is built against the IntelliJ Community platform, so one artifact loads across the family — IDEA, WebStorm, PyCharm, GoLand, RustRover. The minimum supported platform is 2024.2 (build 242).
Enable it for the project
TOVIO registers as a first-class VCS, so it appears in Enable Version Control Integration alongside Git. Pick it there and the native machinery lights up.
What that gets you
Native integration rather than a side panel:
- the native Local Changes view
- the unified VCS Log graph, driven by
tovio log's JSON - a checkout provider, so TOVIO appears under "Get from Version Control"
- a pre-commit conflict gate that warns on unresolved conflicts before a commit runs
- a status-bar widget and project-view file decoration
- a gutter quick-diff against the committed version
Tool window tabs
Changes, History, Stack, Lanes, Security (policies, agents, audit), Semantic Diff, Behavioral, and Output — the last being the CLI log, which is where you look when something misbehaves.
Actions
Clone TOVIO Repository…, Push to Relay…, Pull from Relay…, Sync Lane with Remote, Switch Lane…, New Change…, Land Lane into Main…, Amend Last Commit…, Undo, Redo, Resolve Conflict…, Show Conflict Sides, Check Landability (Health), Why This Line?, Issue Agent Token…, Refresh TOVIO Status, Show TOVIO Output.
Lock File and Unlock File sit in the project-view and editor context menus — the right place for them, because locking is something you do to the file in front of you. Send TOVIO Feedback… sits in the Help menu; the label carries the product name so it cannot be mistaken for the IDE's own feedback item.
Settings
Settings → Tools → TOVIO: the executable path, the status-bar widget, decorations, the refresh debounce, the rationale hover, and token-expiry warnings.
Status: built, less proven
The plugin is implemented and the feature set is broad, but its acceptance evidence is a declared, still-open M5.6 gate. It is usable; it has had less real-world exercise than the VS Code extension. Report rough edges — that is exactly the gap.
It needs the CLI
The plugin owns no version-control logic and no crypto; it spawns tovio and parses its --json output. So tovio must be on the PATH the IDE sees, or its path set in the plugin settings.