---
title: Agent runs, traces and PR history
description: Record scoped agent runs and conversations, check tracker-backed bug drafts for duplicates and inspect candidate pull requests without claiming a proven cause.
seo:
  title: Agent run history, duplicate checks and regression candidates
sidebar:
  label: Agent run history, duplicate checks and regression candidates
---

Loom records agent runs and conversations, checks bug drafts for duplicates and ranks
candidate regression PRs without building the code.

Runs carry goals and outcomes, and model costs when the Claude Code plugin reports the
session's turn usage (on by default). The history covers merged pull requests, review
comments, GitHub issues and, with a tracker source, incidents and CI runs. Conversation
recording, PR history and the tracker are each off until turned on. An agent or a person
can then ask what was tried before, what was decided and which changes to investigate
for a regression.

Duplicate checks need a registered tracker source and a namespace the caller may read.
The [bug draft to candidate PRs](/docs/features/tracker/overview#from-a-bug-draft-to-candidate-prs)
walkthrough covers tracker access and PR-history setup for both operations. Candidate ranking neither runs a bisect nor proves
which change caused the bug.

## What you get

- **Runs.** `run.begin` and `run.complete` record a task's goal, status, the memories the
  agent relied on and what it wrote. [Runs](/docs/features/runs)
- **Conversations and session briefs.** Recorded sessions are searchable, and a session
  brief lets the next session resume. Recording is off until the namespace owner turns it
  on with `conversation.set_logging(enabled=true)`. [Conversations and sessions](/docs/features/conversations-and-sessions) ·
  [Trace and resume long agent runs](/docs/guides/trace-and-resume)
- **PR history.** History of a symbol, path or line, review briefs, a pre-PR duplicate
  check and bisect candidates, as on the [code index page](/docs/use-cases/code-intelligence).
- **Tracker records.** Duplicate issue checks, issue-to-PR links and flaky tests, read live
  from the team's own ClickHouse. Needs `LOOM_TRACKER_ORG` and a registered tracker
  source. [Tracker plane](/docs/features/tracker/overview)
- **Traces and cost.** Loom emits OpenTelemetry and records its own model spend per
  operation; Langfuse and ClickStack are optional sinks.
  [Telemetry](/docs/features/observability/telemetry) ·
  [Cost and usage](/docs/features/observability/cost-and-usage)

## Measured

On public ClickHouse issues, `tracker.duplicate_check` ranked the older issue first for 91
of 104 recorded duplicates (0.875) and called 2 of 100 issues with no recorded link a
duplicate. The result is one tracker's, and its issues (stack traces, error codes,
consistently linked duplicates) are easier than many trackers'.
[Duplicate check on public ClickHouse issues](/docs/benchmarks/results#duplicate-check-on-public-clickhouse-issues)

## Start

[Connect a coding agent](/docs/getting-started/connect-a-coding-agent) installs the
plugins that capture sessions once recording is on; the [code index](/docs/use-cases/code-intelligence)
needs a repository added and `LOOM_CODE_INGEST_ENABLED=true`.

Some ops on this page are marked experimental on the [status page](/docs/reference/status).
