Kelet
I've spent the past few years building 50+ AI agents in prod (some reached 1M+ sessions/day), and the hardest part was never building them — it was figuring out why they fail. AI agents don't crash. They just quietly give wrong answers. You end up scrolling through traces one by one, trying to find a pattern across hundreds of sessions. Kelet automates that investigation. Here's how it works: 1. You connect your traces and signals (user feedback, edits, clicks, sentiment, LLM-as-a-judge, etc.) 2. Kelet processes those signals and extracts facts about each session 3. It forms hypotheses about what went wrong in each case 4. It clusters similar hypotheses across sessions and investigates them together 5. It surfaces a root cause with a suggested fix you can review and apply The key insight: individual session failures look random. But when you cluster the hypotheses, failure patterns emerge. The fastest way to integrate is through the Kelet Skill for coding agents — it scans your codebase, discovers where signals should be collected, and sets everything up for you. There are also Python and TypeScript SDKs if you prefer manual setup. It’s currently free during beta. No credit card required. Docs: https://kelet.ai/docs/ I'd love feedback on the approach, especially from anyone running agents in prod. Does automating the manual error analysis sound right?
AI Analysis
Analysis coming soon.
Similar Products
ParseBench
Show HN: ParseBench – Document parsing benchmark for AI agents
boringBar
Hi HN! I recently switched from a Fedora/GNOME laptop to a MacBook Air. My old setup served me well as a portable workstation, but I’ve started traveling more while working remotely and needed something with similar performance but better battery life. The main thing I missed was a simple taskbar that shows the windows in the current workspace instead of a Dock that mixes everything together. I built boringBar so I would not have to use the Dock. It shows only the windows in the current Space, lets you switch Spaces by scrolling on the bar, and adds a desktop switcher so you can jump directly to any Space. You can also hide the system Dock, pin apps, preview windows with thumbnails, and launch apps from a searchable menu (I keep Spotlight disabled because for some reason it uses a lot of system resources on my machine). I’ve been dogfooding it for a few months now, and it finally felt polished enough to share. It’s for people who like macOS but want window management to feel a bit more like GNOME, Windows, or a traditional taskbar. It’s also for people like me who wanted an easier transition to macOS, especially now that Windows feels increasingly user-hostile. I’d love feedback on the UX, bugs, and whether this solves the same Dock/Spaces pain for anyone else. P.S. It might also appeal to people who feel nostalgic for the GNOME 2 desktop of yore. I started my Linux journey with it, and boringBar brings back some of that feeling for me.
Keyboard First Email Client
My email clients/inbox really fu*ing annoyed me. Tallyman is what happened next: a keyboard driven email client on top of Gmail and Outlook. Your vim muscle memory works (j/k, gg, relative line numbers, counts, ...) 39 rebindable shortcuts, command palette, email templates, themes ... No migration. OAuth only. Verified by Microsoft and live now. Google verification is under review. 30 day free trial, $9/mo per inbox after that. Write me an email if you need an extended trial: contact@tallyman.io
Control your X/Twitter feed using a small on-device LLM
We built a Chrome extension and iOS app that filters Twitter's feed using Qwen3.5-4B for contextual matching. You describe what you don't want in plain language—it removes posts that match semantically, not by keyword. What surprised us was that because Twitter's ranking algorithm adapts based on what you engage with, consistent filtering starts reshaping the recommendations over time. You're implicitly signaling preferences to the algorithm. For some of us it "healed" our feed. Currently running inference from our own servers with an experimental on-device option, and we're working on fully on-device execution to remove that dependency. Latency is acceptable on most hardware but not great on older machines. No data collection; everything except the model call runs locally. It doesn't work perfectly (figurative language trips it up) but it's meaningfully better than muting keywords and we use it ourselves every day. Also promising how local / open models can now start giving us more control over the algorithmic agents in our lives, because capability density is improving.
I built a local data lake for AI powered data engineering and analytics
I got tired of the overhead required to run even a simple data analysis - cloud setup, ETL pipelines, orchestration, cost monitoring - so I built a fully local data-stack/IDE where I can write SQL/Py, run it, see results, and iterate quickly and interactively. You get data lake like catalog, zero-ETL, lineage, versioning, and analytics running entirely on your machine. You can import from a database, webpage, CSV, etc. and query in natural language or do your own work in SQL/Pyspark. Connect to local models like Gemma or cloud LLMs like Claude for querying and analysis. You don’t have to setup local LLMs, it comes built in. This is completely free. No cloud account required. Downloading the software - https://getnile.ai/downloads Watch a demo - https://www.youtube.com/watch?v=C6qSFLylryk Check the code repo - https://github.com/NileData/local This is still early and I'd genuinely love your feedback on what's broken, what's missing, and if you find this useful for your data and analytics work.