I Built an Investigation-First Debugger for AI Agents — TraceMotive v0.3 I just released TraceMotive v0.3.0. TraceMotive is an open-source, local-first debugging tool for AI agent executions. GitHub: https://github.com/doraemonfv-glitch/tracemotive Imagine you have two agent executions. One worked
I Built an Investigation-First Debugger for AI Agents — TraceMotive v0.3 I just released TraceMotive v0.3.0. TraceMotive is an open-source, local-first debugging tool for AI agent executions. GitHub: https://github.com/doraemonfv-glitch/tracemotive Imagine you have two agent executions. One worked. One didn't. Traditional tracing gives you the raw execution data, which is useful — but you still have to answer the hard question yourself: Where should I start looking? That is the problem I wanted v0.3 to focus on. The new workflow is: reference run vs changed run ↓ structural alignment ↓ first evidence-supported behavioral divergence ↓ deterministic findings ↓ investigation starting point The important word here is supported. TraceMotive does not try to guess the root cause. It identifies the first behavioral difference that can be supported by the available structural evidence. v0.3 can produce deterministic findings such as: tool input changed tool output changed new error observed error resolved tool added tool removed execution subtree added or removed tool repetition changed It can also surface context-only changes such as: model changed request parameters changed trace status changed Those context changes do not automatically become the investigation starting point. A debugger shouldn't pretend to know something it doesn't. For example, repeated calls can be difficult to align safely. Consider: Run A: weather() weather() weather() Run B: weather() weather() weather() Pairing the first call on the left with the first call on the right simply because they have the same position can create false matches. TraceMotive deliberately avoids that. When evidence is ambiguous, incomplete, redacted, or unavailable, the result may be: uncertain instead of inventing an answer. v0.3 also introduces a new comparison interface. Instead of showing the full raw comparison first, the UI prioritizes: the investigation state the first supported investigation point evidence observed there additional behavioral observations context uncertainty detailed raw comparison The existing detailed comparison remains available through /api/v2. The new investigation API lives at: GET /api/v3/compare/{left_trace_id}/{right_trace_id} v0.3 includes a deterministic local demo. Install: pip install tracemotive==0.3.0 Start TraceMotive: tracemotive serve Then open another terminal: tracemotive demo The demo creates a reference execution and a changed execution and prints a URL that opens directly in the investigation UI. No OpenAI API key is required for the demo. The privacy model remains important to me. TraceMotive keeps: loopback-only Collector/UI serving local SQLite persistence privacy-controlled content capture redaction before transport no TraceMotive analytics no external TraceMotive telemetry TraceMotive does not prove causality. It does not say: This change caused the failure. It says something closer to: This is the first behavioral divergence supported by the evidence. This is a reasonable place to begin investigating. That distinction became one of the biggest design principles in v0.3. The next big area is broader real-world integration validation. OpenAI Agents SDK is currently the primary validated adapter. I also want to keep testing whether this investigation workflow is actually useful on real agent failures instead of just adding more observability features. If you build AI agents, I'd love feedback — especially examples where TraceMotive becomes too conservative or points you somewhere unhelpful. GitHub: https://github.com/doraemonfv-glitch/tracemotive PyPI: pip install tracemotive==0.3.0
Key Takeaways #
- •I Built an Investigation-First Debugger for AI Agents — TraceMotive v0.3 I just released TraceMotive v0.3.0. TraceMotive is an open-source, local-first debugging tool for AI agent executions. GitHub: https://github.com/doraemonfv-glitch/tracemotive Imagine you have two agent executions. One worked
- •This story was reported by Dev.to, covering developments in the** dev**space. - •AI advancements continue to reshape industries — read the full article on Dev.to for complete coverage.
📖 Continue reading the full article: