> The key insight I'm so tired
[deleted]
Show HN: Kelet – Root Cause Analysis agent for your LLM apps
21–30 of 30 posts
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#22[flagged]
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#23I'm building agent based stuff recently and debugging is indeed pretty painful. It’s hard to even understand where things break
Must say, this looks interesting, I like the idea of clustering failures and trying to find patterns. Feels like something that should exist.
Going to give it a try :)
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#24This looks Amazing Do you have a LiteLLM integration?
regardless notice that LitLLM's been recently heavily compromised, so notice what version you're downloading..
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#25AI agents don’t crash, they just quietly give wrong answers is painfully accurate.. quality RCA is a good direction
curious about how well do the generated hypotheses generalize beyond obvious prompt issues? IMHO lots of failures come from interactions between retrieval, tool selection, and state, more than a single not-so-good description. Do you find the clustering surfaces such multi-factor issues? does it tend to collapse them into prompt-level fixes?
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#26Looks promising!
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#27[flagged]
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#28[dead]
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#29Clustering angle makes sense — individual failures look like noise until you see 50 of them together. Curious tho: can Kelet bootstrap from just user feedback signals, or does it need the SDK instrumentation in place first?
Re: Show HN: Kelet – Root Cause Analysis agent for your LLM apps
#30in the auickstart, the suggested fixes are called "Prompt Patches" .. does that mean Kelet only surfaces root causes that are fixable in the prompt? What happens when the real bug is in tool selection or retrieval ranking for example?
Hi @hadifrt20, OP here From what we discovered analyzing ~33K+ sessions, most of the time when the agent selects the wrong tool, it's because the tool's description (i.e., prompt) was not good enough, or there's a missing nuance here. That goes exactly under Kelet's scope :)
I'll give it a try