Dev builds FailEcho, a scanner that finds agent failures repeating across runs
EvenAd1183 · reddit · 2026-09-16
A developer noticed repeatedly-running agents (nightly scrapes, scheduled reports, queue workers) keep hitting the same external failures — like a recurring 429 — and small local models silently retry and move on without reporting.
He built FailEcho, MIT-licensed and self-hostable:
- Claude Code version: one stdlib-only file reading local logs, surfacing tool failures repeated across sessions (tool names and counts only, no error text or paths)
- Wrapper version: wraps tools in LangChain/LlamaIndex/custom loops, logging failure shape (service, operation, error class, duration) at 3ms overhead
He's also polling the community: what failure does your pipeline keep hitting, and is it unique to your setup or shared?
Related event: FailEcho Helps Agents Remember Past Errors Instead of Retrying Blindly(2 posts)→
More from coding & agent
- How a founder made a Coca-Cola-style AI ad with BlenderMCP and Higgsfield — Fun-Meaning-6474 · 2026-09-16
- Skills vs MCP vs RAG vs Memory: a 4-part framework for what agents actually need to know — MaryamMiradi · 2026-09-16
- 16GB VRAM agentic coding benchmark: Qwen3.8-27B sweeps, K2-Horizon-7B flops — Barni275 · 2026-09-16
- Salesforce launches Koa, its first CRM reasoning model, claiming 3x fewer errors — LiJunnan0409 · 2026-09-16
- Tenex Labs' Build vs Buy Rule: Build What Strengthens Moat, Buy the Rest — thisiskp_ · 2026-09-16
- PixiJS 3D closed beta opens: WebGPU-first, 2D+3D in one API, open-sourcing soon — flngr · 2026-09-16