Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 19 additions & 7 deletions docs/use-cases/runs-and-pr-history.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,24 @@
---
title: Agent run history, duplicate checks and regression candidates
description: Record scoped agent runs and conversations, check tracker-backed bug drafts for duplicates and inspect candidate pull requests without claiming a proven cause.
---

# Agent runs, traces and PR history

Loom records the work coding agents do, as runs and searchable session conversations, and
connects it to your code history. 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
change introduced a regression.
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](../features/tracker/overview.md#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

Expand Down
2 changes: 1 addition & 1 deletion llms.txt
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Start with [the docs map](docs/index.md). To install Loom, a coding agent reads
- [Document search and RAG for agents](docs/use-cases/document-search.md): Loom indexes your documents (Markdown and text, and PDF, `.docx` and `.pptx` files that its extractor service converts) and lets agents search them with citations over MCP, HTTP or the SDKs.
- [Memory linked to code for coding agents](docs/use-cases/memory-linked-to-code.md): Loom links coding agents' memories to the functions, classes and files they name, follows them through refactors, and flags a memory when its code changes.
- [Shared context for multi-agent workflows](docs/use-cases/multi-agent.md): Loom is a self-hosted MCP server for multi-agent memory, with namespace-scoped tokens and separate read and write roles.
- [Agent runs, traces and PR history](docs/use-cases/runs-and-pr-history.md): Loom records the work coding agents do, as runs and searchable session conversations, and connects it to your code history.
- [Agent runs, traces and PR history](docs/use-cases/runs-and-pr-history.md): Loom records agent runs and conversations, checks bug drafts for duplicates and ranks candidate regression PRs without building the code.
- [Self-hosted agent memory on ClickHouse](docs/use-cases/self-hosted-clickhouse.md): Loom runs on your own infrastructure, with Docker or on Kubernetes with its Helm chart, and stores agent memory, documents, conversations and code indexes as tables in ClickHouse.

## FAQ and glossary
Expand Down