# TRAJDEBUG: Tracing Error Lifecycle to Identify Critical Failures in Long-Horizon Agent Trajectories

Source: [arXiv](https://arxiv.org/abs/2608.06346v1)  
Feed7 permalink: https://feed7.dev/p/2608-06346v1-125r9ui  
Published: 2026-08-06T17:51:20.000Z  
Trust: Needs Review (needs_review)

## Why Included

TrajDebug tracks whether errors persist, resolve, or cause terminal failure, offering a sharper way to debug long coding-agent runs than flagging every local mistake.

## Source Summary

**TrajDebug** compresses long histories at multiple granularities, identifies errors from evidence, then tracks resolution status and terminal impact. **TrajErrBench** contains **486 manually annotated failed trajectories** from Tau2Bench and SWE-Bench Pro.

## Practical Implication

For coding-agent observability, preserve enough trajectory context to distinguish a harmless local mistake from the earliest unresolved error that caused the final failure. That attribution can make remediation more targeted.

## Agent-Ready Context

**TrajDebug** compresses long histories at multiple granularities, identifies errors from evidence, then tracks resolution status and terminal impact. **TrajErrBench** contains **486 manually annotated failed trajectories** from Tau2Bench and SWE-Bench Pro.

For coding-agent observability, preserve enough trajectory context to distinguish a harmless local mistake from the earliest unresolved error that caused the final failure. That attribution can make remediation more targeted.

The abstract claims the best overall performance and actionable downstream feedback but gives no scores or baseline details. Code and data are promised for release, so reproducibility cannot be assessed from this material.

## Connected Context

Feed7 judgment across 390 accumulated Signals:

This turns long-trajectory inspection into lifecycle attribution: identify errors from evidence, track whether they were resolved, and isolate the earliest unresolved mistake linked to terminal failure. It operationalizes prior calls for queryable trajectories and flexible analysis, while going beyond pass/fail verification toward targeted remediation. The absent scores, baseline details, code, and data keep the claimed advantage provisional.

- [The Future of Evals: From LLM as a Judge to Agent as a Judge — Aparna Dhinakaran, Arize AI](https://feed7.dev/p/the-future-of-evals-from-llm-as-a-judge-to-agent-as-a-judge-aparna-dhina-1fu560o) — TrajDebug supplies a concrete agent-analysis task for failures that fixed rubrics miss: follow errors across a variable trajectory and distinguish resolved mistakes from terminally consequential ones.
- [Everything Is a Rollout — Alex Shaw + Ryan Marten, Terminal-Bench, Harbor, Laude Institute](https://feed7.dev/p/everything-is-a-rollout-alex-shaw-ryan-marten-terminal-bench-harbor-laud-0iz4rgx) — Harbor’s reproducible rollout loop provides the trajectories and verified outcomes that TrajDebug needs; TrajDebug adds causal error attribution to their inspection.
- [Rethinking Environments for Long-Horizon Work — Rayan Garg, Theta Software](https://feed7.dev/p/rethinking-environments-for-long-horizon-work-rayan-garg-theta-software-11r7wbx) — Multi-granularity history compression is an implementation response to the requirement that long traces remain queryable, while terminal-impact tracking preserves the link to final-state evaluation.
- [Form, Not Content? A Preregistered, Placebo-Controlled Evaluation of Learned Error-Conditioned Self-Repair Through Prompts and Weights in Frozen Small Code Models](https://feed7.dev/p/2607-12962v1-0q4i26c) — The placebo-controlled repair result warns that feedback labeled as an error may not be causally informative; TrajDebug’s evidence-based attribution could help distinguish actionable failure content, though its remediation benefit remains unquantified.

## Context Map

- Layer: benchmark
- Domains: coding
- Topics: agent-evals, agent-reliability, observability

## Uncertainty

- The abstract claims the best overall performance and actionable downstream feedback but gives no scores or baseline details. Code and data are promised for release, so reproducibility cannot be assessed from this material.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.