Skip to main content
agentcompass analysis re-runs analyzers on an existing AgentCompass result directory without re-running the agent:
Analyzers inspect trajectories, metrics, errors, latency, model output, and tool calls, then attach analyzer output under analysis_result.<AnalyzerId>. Use analyzers when a benchmark score tells you what failed but not why it failed.

What Analyzers Do

Badcase detection

Flag exceptions, truncation, JSON errors, repetition, empty outputs, latency spikes, and terminal misuse.

Statistics

Compute step counts, tool-call counts, durations, token lengths, value counts, and numeric summaries.

Qualitative diagnosis

Use LLM-backed analyzers to annotate trajectory phases, summarize behavior, and render reports.

Aggregation

Aggregate analyzer output into analysis_summary.json and analysis_summary.md.
Analyzers do not rerun agents or rescore benchmark correctness. They read completed task results.

Run With Evaluation

Use this path when you know which analyzers should run as part of the evaluation.

Re-run On Existing Results

By default, analysis copies the input run into a new timestamped sibling. Use --output to choose the copy destination or --override when you intentionally want in-place mutation.

Options

The default copy protects the measured run from accidental mutation. Use --override only when replacing its existing analysis data is intentional and no immutable archive depends on that directory.

Selection Rules

Supported Families

Use agentcompass list analyzer to inspect the analyzers registered by the installed revision. Common families include:

Output Shape

Per-task details keep analyzer output under:
Aggregated summaries group analyzers by category and render:
  • total analyzed tasks;
  • badcase count and badcase ratio;
  • average score when provided;
  • value-count distributions;
  • numeric min, max, mean, and p95 stats.