Vibin' and Koverin'
In Which the Author Wonders if This Coding Agent Comes With a Baguette
A brief update from my weekend's work...
As part of getting a handle on the capabilities of coding agents more broadly, I spent time this weekend trying out Mistral's Vibe CLI, paired with its mistral-medium-3.5 model. The TUI is decent, roughly on par with OpenCode and in the ballpark of Claude Code. The model is closer to Claude Haiku than Claude Sonnet, which is disappointing. It is usable, but only with pretty strong guardrails, and even then it struggles without detailed instructions to follow. C'est la vie.
BTW, in case you were wondering what Claude Code, Gemini, Copilot, etc. all use for their TUIs... it's Ink. I am uncertain if Mistral's CLI uses Ink, but it has that... vibe. 😁
This weekend, I also released koverGate 0.5.0.
One breaking change: if you put a koverGate {} configuration block in your root build.gradle.kts file, and you tried setting coverage gates there, those used to be silently ignored. koverGate does not presently support whole-project coverage gates, just per-module. Now, setting coverage gates in the root build.gradle.kts fails with an error, as that particular koverGate {} only supports prettyPrintJson. This more accurately reflects what koverGate actually does, at the cost of a one-time update to a Gradle file for users. Sorry!
The changelog points out other improvements, including:
- A new
koverGateBumpGradle task to suggest new coverage gate lines to use for a module, reflecting the now-current coverage levels
- More detailed coverage information in the gap report, specifically around partially-covered lines
- Even more steps are taken to help inform your agents when koverGate seems to be working off of stale Kover reports
Add a comment: