This is so funny, i've been working on my HN post for the past hour, then i saw this :)
Anyway, in practice, I saw it go from 5-6 print-debug cycles down to 1-2 targeted stops.
I built a small CLI that wraps the Debug Adapter Protocol and exposes basic debugger actions so agents can call them directly. Each command blocks until execution pauses, then returns the full context.
The CLI is just a thin layer. The useful part is a debugging “skill” on top that teaches the agent how to debug methodically with it, define clear hypotheses, validate/invalidate them, etc.
Anyway, in practice, I saw it go from 5-6 print-debug cycles down to 1-2 targeted stops.
I built a small CLI that wraps the Debug Adapter Protocol and exposes basic debugger actions so agents can call them directly. Each command blocks until execution pauses, then returns the full context.
The CLI is just a thin layer. The useful part is a debugging “skill” on top that teaches the agent how to debug methodically with it, define clear hypotheses, validate/invalidate them, etc.