Projects

Agent Autopsy — Forensic Debugger for Failed AI Agent Runs

Active
Next.js 16TypeScriptApp RouterOllama (qwen3:14b)Vitest
Product demo

Problem

Most AI agent failures are silent — the run completes, the status code is green, and the result is still wrong. Observability platforms show you the trace, but never the cause of death.

Business Impact

Teams ship agents that fail silently and only hear about it from angry users. Agent Autopsy turns an opaque transcript into a one-line cause of death, so engineers stop guessing and start fixing — without shipping private traces to a third-party SaaS.

System Approach

  • Next.js 16 App Router app with the forensic engine in lib/autopsy.ts
  • scan + diagnose API routes: heuristic classifier first, optional LLM pass second
  • Five explicit failure signatures detected from transcript structure, not vibes
  • Optional local Ollama (qwen3:14b) pathologist's note for root cause
  • 6 Vitest tests covering the signature classifier

Key Decisions & Trade-offs

  • Heuristics-first for an instant verdict — the LLM is an optional deepening, not the critical path
  • Local LLM over cloud — agent traces are sensitive and stay on the machine
  • Five named signatures over a black-box score — engineers want a cause they can act on
  • Zero runtime dependencies in the engine — rebuilt from a v1 single-file prototype with no shortcuts

Current Status

Public and open source (MIT) at github.com/rohitguta2432/agent-autopsy. Heuristic verdicts plus optional local qwen3:14b diagnosis working; 6 Vitest tests passing. The 15-second demo diagnoses the app's own sample corpse on camera.

Roadmap

  • Add more failure signatures (silent truncation, tool-arg drift)
  • Framework adapters to import LangChain / CrewAI transcripts directly
  • Shareable report links for team triage

What I'd Improve Next

  • A hosted demo with a bundled small model so no local setup is needed
  • Batch autopsy mode to run inside CI on every failed agent run

Explore More