Why I Built Agent-Devtools After a Brutal Debugging Nightmare
Heat trend
Collecting trend data
The percentage is based on available heat signal, not comment count or independent people.
The developer created Agent-Devtools after a frustrating debugging experience where their AI agent repeatedly hallucinated tool calls and consumed the token budget.…
I remember it was 4:30 PM, and my terminal was basicaly a wall of endless, scrolling text. My AI agent had just gone completely off the rails for the fourth time in a row, hallucinating tool calls and eating through my token budget like candy. I was staring at thousands of lines of raw JSON, cross-eyed and exhausted, trying to figure out HOW things went so wrong.
That brutal day of debugging is exactly why I built Agent-Devtools. Instead of digging through a messy text log, it now gives me a decently clean, interactive visual timeline that maps out the exact path my agent took. I can see the prompt payload, click on the exact step where it drifted, and spot the bug in seconds instead of hours. If you've ever felt that despair of debugging blind, this might really help you.
This is the Repo if you had these type of nightmares 🙏: https://github.com/Jacopos311/Agent-Devtools
There is a short GIF in the README along with some pictures and documentation that might help you understand a bit better how it works, i hope that this resource, even if not perfect, will help at least some of you.