# Agent replay that makes failures reviewable

When an agent gate fails, reviewers need the path — not a summary. AgentClash replay timelines show tool calls, observations, artifacts, and scorecard context in one place.

Source: https://www.agentclash.dev/features/agent-replay
Markdown export: https://www.agentclash.dev/md/features/agent-replay

## Why replay matters

Replay turns agent eval from a score into an auditable story of what the agent tried and what the environment returned.

- OpenTelemetry-compatible trace import
- Pinned datasets and golden test cases
- Baseline versus candidate regression checks
- Replay trails for tool calls, outputs, and artifacts
- Scorecards for correctness, cost, latency, and evidence
- CI gates for prompt, model, RAG, and tool changes

## Replay workflow

### 1. Import the evidence

Start from OpenTelemetry traces, curated datasets, support transcripts, or a real failure your team already saw.

### 2. Pin the baseline

Record the current accepted behavior so every prompt, model, RAG, or tool change has a fair comparison point.

### 3. Replay the evidence

Inspect tool calls, outputs, artifacts, latency, cost, and judge evidence when a candidate gets worse.

### 4. Gate the release

Compare candidate and baseline runs, then fail CI before a regression reaches users.

## Debug with docs

Pair replay with interpret-results guidance and challenge packs so every debugged failure becomes a reusable test.

- [Agent evals](https://www.agentclash.dev/agent-evals): Real-task agent evals with replay evidence and CI gates.
- [LLM agent evaluation](https://www.agentclash.dev/llm-agent-evaluation): Evaluate LLM agents on full trajectories, not one-shot answers.
- [Compare tools](https://www.agentclash.dev/compare): See how AgentClash differs from prompt-eval platforms.
- [Trajectory evaluation](https://www.agentclash.dev/agent-trajectory-evaluation): See how replay supports full-path agent scoring.
- [Datasets overview](https://www.agentclash.dev/docs/guides/datasets-overview): Import examples, record baselines, sync regression suites, and gate CI.
- [Dataset CI gates](https://www.agentclash.dev/docs/guides/dataset-ci-gates): Fail builds when a candidate regresses against a pinned baseline.
- [CI/CD agent gates](https://www.agentclash.dev/docs/guides/ci-cd-agent-gates): Block pull requests when agent behavior gets worse.

## Agent replay FAQ

### What does AgentClash replay include?

Tool calls, observations, logs, artifacts, timing, and links to the scorecard dimensions that passed or failed.

### Can replay be shared with reviewers?

Yes. Runs support shareable views so PMs, support leads, and engineers can review the same evidence.

### How does replay help CI failures?

When a gate fails, replay shows exactly which step diverged from baseline so you do not guess from a single error string.