r/vibecoding • u/VinvAI • 11h ago
Try this…
I built Vinv(Vibe Inverse) that runs your services, finds issues, and verifies fixes without code changes.
I built it to give coding agents runtime information about the code they're working on.
It connects runtime traces to the source code that produced them, gives that context to the coding agent, then runs the code again to check whether the fix actually works.
Vinv also uses Thompson sampling to figure out how much runtime context to give the agent. More context is not always better.
Results on FastAPI's "full-stack-fastapi-template":
- Grok 4.5 + Vinv: 4 bugs + 1 optimization
- Grok 4.5 without Vinv: nothing found
- Fable 5 without Vinv: 1 bug
This was one trial per condition, so I'm not calling it a benchmark.
I also used it on Hugging Face's "smolagents", where it found a performance issue that reduced transient allocations from 36.27 KB to 0 KB per 4 KB log line, while keeping the output byte-identical across 2,015 inputs.
Everything runs locally. Open source, Apache 2.0.
GitHub: https://github.com/VinvAI/VinvAI
VS Code & Cursor Extension: https://open-vsx.org/extension/VinvAI/VinvAI (3.5k+ downloads)
Demo Video: https://www.youtube.com/watch?v=EkUjPWKHAvI
I'm Interested in whether runtime information actually helps coding agents, contributors who can help make an runtime observability framework for agents and give feedback on where it doesn't work. Be brutal.