Arthi Arumugam

whatbroke goes live here in about an hour, and there's one thing I genuinely can't answer from my own desk.

It diffs two agent runs and shows what changed between them: which tool calls fired, how the arguments differed, what each run cost, where the outputs diverged. The importer currently reads plain JSONL, OpenTelemetry, Langfuse and LangSmith exports.

Four formats is where I ran out of things I use myself, not where the problem ends. So: what are you exporting traces as right now? If it's none of those four, I'd rather know today than guess at the next importer.

Second question, and this one I'm too close to judge. The output is a terminal report with BROKE and CHANGED blocks, before/after lines for arguments, and a cost and latency delta per case. Is that readable to someone who didn't write it, or does it need a legend?

Hi Vibecoders, I have built something I have previously many times faced issues with. I published an app and made 9 bucks and was so happy until I got someone telling me the security is weak. I thought it was a dummy threat but I went in and there it was. Exposed keys. Open API routes. No security headers. The whole thing was naked. That's why I build Vibesafe - seriously. Vibe. Safe. People assume vibe-coding is just a click of a button and voila you have a million dollar machine. There is struggle, endurance and diligence behind every build and direction. So Vibesafe and feel free to ask any questions you have. Thank you for the chance!