Back to Overview

Re-Read Rate

Agent Behavior

· 54 PRs with data in past 30d (116 total)

Count
54
Average
2.15
↓ 0.27 vs prior 30d
P10
1.17
↓ 0.12 vs prior 30d
P50
2.09
↓ 0.28 vs prior 30d
P90
3.22
↓ 0.43 vs prior 30d

Trend

Distribution

0.5–1.0
3
1.0–1.5
9
1.5–2.0
11
2.0–2.5
14
2.5–3.0
7
3.0–3.5
9
3.5–4.0
1

Notable PRs

Highest
#250Refactor form validation library3.67
#133Fix CORS headers for preflight3.47
#147Optimize Redis connection pooling3.43
Lowest
#241Optimize bundle size with tree shaking0.83
#125Add Prometheus metrics endpoint0.96
#157Add retry logic for webhook delivery0.98

About This Metric

Re-Read Rate

What It Measures

The ratio of total file reads to unique files read across sessions correlated to a PR. A value of 1.0 means every file was read exactly once; higher values indicate files were read multiple times.

Why It Matters

When the model re-reads the same file multiple times in a session, it typically means one of: the file is too large to retain in context, the model lost track of information it read earlier, or the task required revisiting the same code repeatedly.

Re-reading burns tokens without adding new information. While some re-reading is normal (checking a file after modifying it), excessive re-reading suggests the model's context management could be improved — for instance, by providing better summaries in CLAUDE.md, using partial reads with offset/limit, or keeping files smaller.

How It's Calculated

re_read_rate = total_file_reads / unique_files_read

Where total_file_reads counts every Read tool invocation and unique_files_read counts distinct file paths read (already tracked as files_read_count). Summed across all correlated sessions. Returns null if no files were read.

Data Sources Required

  • Claude Code session data — Count of Read tool invocations (total) and unique file paths read.