Kelet vs Libretto

Kelet is a root-cause analysis agent for LLM applications that goes beyond trace visualization. Where most observability tools stop at showing you what happened, Kelet automatically reads your traces, cross-references failure patterns across thousands of sessions — thumbs-down ratings, abandoned conversations, LLM-judge flags — generates root cause hypotheses, and produces targeted prompt patches to address them. The workflow is: connect your traces (LangSmith, Langfuse, or direct API), let Kelet ingest your failure signals, and receive a prioritized list of failure clusters with explanations and draft prompt fixes. SOC 2 Type II certified, read-only access to traces — nothing is mutated. The indie team positions it as the missing "closing of the loop" in LLM observability: most teams can detect failures but have no systematic path from detection to fix. The HN thread surfaced a real pain point: teams know their chatbot is failing somewhere, but diagnosing which prompts, tools, or routing decisions are responsible requires manual trace archaeology. Kelet automates that archaeology and produces actionable output, not just dashboards.

Libretto is an open-source browser automation toolkit built by Saffron Health to solve a critical problem with AI-driven web agents: non-determinism. Standard agent-controlled browsers using Playwright or Puppeteer routinely fail 20-30% of the time on production workflows because they rely on LLM judgment for timing and element selection. Libretto replaces that with a record-replay system that captures precise interaction timing and DOM fingerprints, achieving a reported 95% success rate on identical workflows. The library works by recording a "golden path" of a browser session — capturing not just actions but the exact CSS selectors, visual context, and timing windows during which those actions are valid. On replay, it verifies each step against expected page state before proceeding, and falls back to an LLM-assisted recovery mode when pages drift (e.g., after a UI update). Saffron Health built it to maintain integrations with EHR portals that change frequently and where failure has compliance consequences. Saffron open-sourced Libretto after using it internally for 18 months across 40+ healthcare software integrations. The HN thread highlighted the appeal for fintech, legal, and healthcare automation where reliability, not just capability, is the product. The toolkit targets TypeScript/Node.js environments and integrates cleanly with existing Playwright infrastructure.