<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/bcef1180635c4420a8feb78a64279b87&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bcef1180635c4420a8feb78a64279b87-07b5d71685a23910.gif</thumbnail_url><duration>122.424</duration><title>Catching and Fixing AI Agent Errors</title><description>This Loom explains a project for catching and correcting AI agent errors before they handle real cases in a harness testing environment. The speaker notes that failures are otherwise hard to diagnose because there is no visibility into the cause. They simulate customer returns objective scenarios where AI agents can make inconsistent decisions by skipping evidence, misleading policy exceptions, or repeating mistakes. The UI runs iterations on three scenarios, including eligible returns, delivery group misses, and defect exception, and updates two files with trace fields showing why Atlas ejects due to reaching a limit.</description></oembed>