Vinv is an IDE plugin that auto-exposes its MCPs to all coding harnesses on your system. It gives harnesses the same runtime information and context about the repo you are working on, connects runtime traces to the source code, provides context for the coding agents, and reruns the code to verify that the fix works. It uses Thompson sampling to figure out how much runtime context to give the agent. Everything runs locally. Open source, Apache 2.0.
This came from watching my coding agent confidently "fix" an endpoint
that was still 500-ing. The gap in agentic coding isn't the model -it's
that nothing independently checks what actually happened at runtime.
Vinv sits between your agent and your running backend: it records the real
run, hands the evidence to your agent over MCP, then re-verifies the fix
itself (fresh process, live port, hidden acceptance tests).
Would love your feedback on the verify loop.
Report
Maker
@new_user_314d2213c0 glad it could give your agent the call tree and evidence it needed to cut through the noise and debug.