Reading an execution trace

A trace is the answer to "why did it do that". Steps are written as they happen, so a run that crashed still shows how far it got.

The step types

• •Planning — the model took a turn and decided what to do next.
• •Tool proposed — it asked for a specific call. This records the *raw*

arguments, before validation, so you can see what it wanted rather than what we allowed.

• •Validation failed — the tool does not exist, this agent does not have it,

or the arguments did not match the schema.

• •Policy denied — the call was understood and refused.
• •Approval required — it stopped for a human.
• •Tool executed / failed — it ran, with timing.
• •Response generated — it answered.

Why refused calls are shown

A trace that only showed successful calls would hide the most interesting thing about a run: the moment something was stopped. The difference between what was proposed and what was allowed is usually the answer you are looking for.