#debugging
Every post tagged "debugging".
34 posts · showing 31–34
-
Assert on the Trajectory, Not the Answer
A final-answer check will happily pass a run that took nineteen turns and touched a tool it should never have called. Five lines of trajectory assertions catch what output tests structurally cannot.
-
Why Your Agent Stops Too Early: The Missing Termination Signal
"Done" in most agent loops means the model stopped asking for tools — indistinguishable from stuck, confused, or bored. Making completion an explicit, validated claim takes about twenty lines.
-
Your Agent Isn't Thinking, It's Looping — Read One Turn of the Trace
There's no reasoning engine and no memory — just a while-loop, a stateless model, and an array that grows. Unroll one turn of it and most agent mysteries stop being mysteries.
-
Why Your Agent Forgets Step 2 by Step 7 — And Four Ways to Keep the Thread
Agents rarely fail because they reason badly — they fail because the original instruction gets buried under accumulated tool output. Here's how to tell displacement from dilution, and four fixes that keep the thread intact.