fruxon-debug-trace
Work out why a run did what it did, from its execution trace: find the run, read the step tree, drill into a tool call's parameters and result, and reconstruct the state the agent decided from. Load when a run failed, hung, or produced a surprising result — including the common case of a run that reports COMPLETED but did the wrong thing.
Pinned to revision 91b14833e806, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.