REPLAY AND DEBUGGING

KEEPING NOTES WHILE YOU DEBUG Write down each guess and each result as you go. Notes prevent you from repeating the same test, help a teammate take over mid-investigation, and become the raw material for the postmortem. A short list of what you tried and what you saw is enough. EXAMPLES Example 1: A replay An engineer re-runs the recorded inputs, tool outputs, and settings of a failed session in a safe offline setting. She watches step by step to see where the agent went wrong. Example 2: Recording tool responses A bug does not reproduce because the live database has changed. Because every tool response was recorded, the replay uses the old data and the failure appears again. Example 3: A stale source An answer looked wrong, but the agent was correct about the data it received. The root cause was a stale data source, so the model was left alone and the source was fixed. Example 4: Two kinds of problem One trace shows a tool call returning HTTP 503, which is a tool problem. Another shows a successful tool call followed by a wrong conclusion, which is a reasoning problem. PRACTICE LAB CONNECTION Replay a recorded Resume Review Agent lab session from Chapter 68. Test the prompts below against the bug injected into that chapter.