Rikin Shah

Hi, I'm Rikin, maker of dotpals (a small open-source pal that shows what your AI coding agents did). Most people seem to use Jev for lead-gen and booking calls. I'm using it for something different: as a judge for test results. My coding agent says "All tests pass. Done!" far too often. dotpals reads the test runner's own output first, and when the output and the exit code disagree, it sends Jev a short, redacted snippet and asks one question: "did these tests pass?"

It answers in about 0.2 seconds with a probability. In the first day it caught a real false "pass" (a run where the tests never actually ran) at 92% certainty, and it rated our own 148-test suite as passed, 98% sure.

Hey everyone, I'm Rikin, the maker of dotpals. I built it because my friend vibe codes all day: the agent says "Done!", and he had no idea which files changed, what failed, or whether anything was really tested. dotpals turns hundreds of tool calls into a few plain lines, reads the test runner's own output instead of trusting "Done!", and flags things like a .env edit or code changed after the tests passed. The best features so far came from stories like these (the test-output check came from one X comment). So I'd love to hear yours: what did your agent do that you only caught afterwards? A silent force-push? "All tests pass" when none ran? A file it touched that it shouldn't have?

I'll use the answers to decide what dotpals should catch next!!