Most LLM agent debugging is vibes-based: edit a prompt, eyeball the output, repeat. agent-lens makes it structuralPause a running agent at any LLM call. State a hypothesis. Fork with edited messages. Get a structural diff — latency, tokens, cost — with verdict: improved/regressed.No other tool has pause, fork, or run diff. Local-first, SQLite, zero infra. pip install agentlens-tracer
Hey PH! I'm Raju, maker of agent-lens.
The frustration that started this: every prompt change is a hypothesis test, but the only tool we have is eyeballing two outputs in two terminal windows. No record of why you made each change. No structural way to know if it actually helped. agent-lens adds the missing layer: pause your agent at any LLM call, write down your hypothesis, fork with the edit, and get a diff with exact numbers. The note travels with the run forever — future you can read your reasoning, not just see the final code.
Zero infra. SQLite on your machine. No API keys needed to start.
Happy to answer anything — what's your biggest pain point debugging LLM agents?
Report
No reviews yetBe the first to leave a review for agent-lens