Know exactly what
changed between sessions.

BranchPy's Compare tool diffs any two analysis reports side by side — new issues, resolved findings, added or removed labels, and structural changes — all in one view inside VS Code.

✓ New / fixed issue tracking 🔀 Label-level diff 📅 Timestamped history ⚡ One-click last-two compare

Reports stack up. Reading each one manually doesn't scale.

Every BranchPy analysis produces a timestamped report. After a few sessions you have five, ten, twenty reports. Manually opening two JSON files and scanning for differences is error-prone and slow — especially when you're mid-sprint trying to verify a fix.

Compare loads two reports, aligns them by label, and shows you exactly what moved, what was added, and what was resolved — with filters, export, and one-click navigation back to the source.

What a comparison looks like

Labels are aligned by name. Changes are colour-coded per row so you can see the delta at a glance.

BASE — report_2026-03-01.json
COMPARE — report_2026-03-10.json
chapter2_intro
3 errors · 1 warning
FIXEDchapter2_intro
0 errors · 1 warning
path_trust
0 errors · 0 warnings
NEWpath_trust
1 error · 0 warnings
Variable gift_given read before assignment · line 74
— not present —
ADDEDchapter5_prologue
0 errors · 2 warnings
REMOVEDsecret_ending_cut
Was: 0 errors · 1 warning
— not present —
start
0 errors · 0 warnings
start
0 errors · 0 warnings

What Compare tracks

🟢

Fixed issues

Labels that had errors or warnings in the base report but are clean in the compare report. Confirms your fix actually worked.

🔴

New issues

Labels that gained new errors or warnings since the base run. Catches regressions introduced in the current session before they compound.

Added labels

Labels that exist in the compare report but weren't in the base — newly written scenes and chapters appear here with their initial quality state.

Removed labels

Labels present in the base but gone from the compare run. Catches accidental deletions or label renames that leave dangling jumps elsewhere.

⚡ One-click last-two compare

The most common workflow — comparing the current run to the previous one — is handled by a single command: Compare Last Two Reports. BranchPy automatically selects the two most recent timestamped reports and opens the diff view. No file picker, no manual selection.

For deeper history review, the full picker lets you select any two reports by timestamp. Reports are listed with their date, total issue counts, and label counts for quick orientation.

What you get right now

Compare is available in BranchPy for Ren'Py Free and above.

One-click last-two compare

Single command compares the two most recent reports without any file selection. Instant feedback on whether your last session improved or regressed the project.

🗂️
Any-two report picker

Browse all stored reports by timestamp. Select any pair for a deep-history diff — useful for milestone reviews or regression investigations.

🔎
Filter by labels, jumps, or issues

Narrow the comparison view to only the data you care about — see only new errors, only changed jump targets, or only labels you modified today.

📤
Export diff results

Export the comparison as JSON or a formatted summary for changelogs, PR descriptions, or review handoffs.

What's coming next

Compare v1 One-click last-two compare · Any-two picker · Label-level diff · Filter by labels/jumps/issues · Export · Automatic change notifications ✓ Done
Lane role labels BASE and COMPARE badges with tooltips for clear lane identification in the diff panel ✓ Done
Variable state diff Show how PILOT-tracked variable ranges changed between runs — which bounds narrowed, which expanded Upcoming
Timeline view Visual quality trend across all stored reports — issue count over time, heat map of most-changed labels Planned

Ready to actually know what you changed today?

Install BranchPy for VS Code. Run two analyses. Open Compare in under a minute.

Get BranchPy Read the docs