branchdiff

Visual git & file diff in your browser — with AI-supported code review & resolve, GitHub & Bitbucket sync, and persistent sessions. 100% local, no cloud, no telemetry.

Open any git diff in a browser UI with inline comments, split/unified views, and syntax highlighting. Use Claude Code slash commands (/branchdiff-review, /branchdiff-resolve) or any AI via prompts to review and fix code. Push and pull review comments to GitHub and Bitbucket PRs. Everything runs on your machine.

Features: inline diff comments · AI review & resolve (Claude Code or any AI) · GitHub & Bitbucket PR sync (browser + CLI) · persistent sessions across commits · three diff modes (git, file, delta) · code tours · keyboard navigation · multiple repos simultaneously

Jump to:

• Install
• Common tasks
• AI Review
• Usage Guide
• Keyboard Shortcuts
• Why branchdiff?
• Features
• Guideline
• Changelog
• License
• Support
• Acknowledgments

Install

Quick start (Node.js required):

npm install -g @encryptioner/branchdiff

Other options:

• pnpm add -g @encryptioner/branchdiff (pnpm)
• yarn global add @encryptioner/branchdiff (yarn)
• pip install branchdiff (Python — no Node.js needed)
• brew tap encryptioner/branchdiff https://github.com/encryptioner/branchdiff-releases && brew install branchdiff (Homebrew)
• Standalone binaries from GitHub Releases (no Node.js needed)
• npx @encryptioner/branchdiff main..feature (one-time, no install)

Tab-completion installs automatically — restart your terminal after install.

Requires git on your PATH. Node.js 18+ is needed only for npm/pnpm/yarn installs (not required for standalone binaries).

See the full installation guide for platform-specific instructions (Homebrew, Scoop, pip, apt, standalone binaries).

Common tasks

| I want to… | Command | |---|---| | See my uncommitted changes | branchdiff | | Compare with main | branchdiff main | | Compare two branches | branchdiff main feat | | View a GitHub PR | branchdiff https://github.com/owner/repo/pull/123 | | View a Bitbucket PR | branchdiff https://bitbucket.org/workspace/repo/pull-requests/123 | | Browse repo files | branchdiff tree | | View last commit | branchdiff HEAD~1 | | Compare branch vs parent | branchdiff -p | | Compare branch vs 3rd commit back | branchdiff -p 3 | | Only unstaged changes | branchdiff -p 0 | | Check PR status | branchdiff pr info | | Merge a PR | branchdiff pr merge | | Push comments to PR | branchdiff sync push | | AI agent reference | branchdiff agent guide | | Dark mode / unified view | branchdiff main --dark --unified |

Any ref works: branch name, commit SHA, tag, HEAD~N, origin/<branch>.

AI Review

Review and fix diffs with any AI assistant — no plugin, no MCP server, no special setup.

Comments persist across commits when comparing named branches (branchdiff main..feature). Start a fresh review with the "New review" button in the toolbar, or branchdiff main..feature --new.

Step 1 — start branchdiff (leave it running):

branchdiff main feat          # compare two branches
branchdiff                    # review uncommitted changes
branchdiff HEAD~3             # review last 3 commits

Step 2 — pick your AI:

Claude Code — install skills once, then use slash commands:

branchdiff skill add   # creates .claude/skills/branchdiff-{review,resolve}/SKILL.md

| Slash command | What it does | |---|---| | /branchdiff-review | AI reads the diff and posts inline comments | | /branchdiff-review main feature | Review a specific branch comparison | | /branchdiff-resolve | AI reads open comments and makes the code fixes |

Any other AI — copy-paste one of these prompts:

Review:

You are reviewing code using branchdiff agent commands (not any other tool).
Run `branchdiff review guide` first to load the full reference, then:

1. Check for prior review context (nth-time review):
   branchdiff agent list --status resolved --json
   branchdiff agent list --status dismissed --json
   - Do NOT re-raise resolved issues — the author already addressed them.
   - Only re-flag dismissed issues if new evidence contradicts the dismissal reason.
   - Acknowledge improvements when the author addressed prior feedback.

2. Run `branchdiff agent diff` to read the full diff.

3. For each changed file, read the ENTIRE file (not just diff hunks) for full context.
   Analyze: data flow (null/undefined?), state/lifecycle (resource cleanup?), contracts (callers updated?), boundaries (input validation?), edge cases.

4. Validate each finding before commenting — re-read surrounding code, grep for imports, read actual call sites.
   Flag: logic errors, security issues, race conditions, broken contracts, missing tests.
   Skip: style, linter-catchable issues, pre-existing problems in unchanged code.

5. Post comments (order: [must-fix] first, then [suggestion], then [question]):
   branchdiff agent comment --file <path> --line <n> --body "[tag] message"
   Tags: [must-fix] bugs/security/data-loss · [suggestion] improvements/missing tests · [question] unclear
   For multi-line: add --end-line <n>

   Tone: lead with the problem, not a judgment. "This returns undefined when X is empty" not "this is wrong".
   Use collaborative language ("Consider using X" not "You should"). Acknowledge good code.

6. General comment (optional): 3+ findings → summarize themes.
   branchdiff agent general-comment --body "<overall summary>"

7. Confirm: branchdiff agent list --status open
Start: branchdiff review guide

Resolve:

You are resolving open review comments using branchdiff agent commands.
Run `branchdiff review guide` first to load the full reference, then:

1. Run `branchdiff agent list --status open --json` to get open threads.

2. For each thread:
   - Skip general comments (filePath "__general__") — these are summaries, not actionable.
   - Skip threads where the last comment is an agent asking a question and the user hasn't responded.
   - Read the comment body to understand the requested change. Interpret intent:
     code suggestion → make the change; documentation suggestion → update docs; unclear → ask for clarification.
   - Read the ENTIRE source file around the commented lines for full context, then make the fix.
   - Resolve: branchdiff agent resolve <id> --summary "Fixed: <what you did>"
   - Or dismiss if the fix shouldn't apply: branchdiff agent dismiss <id> --reason "<why>"

3. Confirm: branchdiff agent list
Start: branchdiff review guide

Or pipe to a CLI AI tool (no session needed):

branchdiff review context | claude -p "review for security"
branchdiff review context --refs "main feature" | claude -p "review these changes"
branchdiff review run --exec "claude" --mode review

What do you want to do?

| I want to… | Go to | |---|---| | Have AI review the diff and post comments | Review workflow | | Have AI fix the open comments | Resolve workflow | | Create a guided code tour for onboarding | Tour workflow | | Get a PR summary / review summary | Summary workflow | | Run a focused security scan | Security audit | | Find untested code paths | Test coverage gaps | | Check for breaking API / schema changes | Breaking-change review | | Review added/changed dependencies | Dependency review |

Option A — Claude Code: install skills once

branchdiff skill add    # creates .claude/skills/branchdiff-{review,resolve}/SKILL.md

Then use slash commands — no prompt needed:

• /branchdiff-review — AI reads the diff, posts inline comments with severity tags
• /branchdiff-review main feature — review a specific branch comparison
• /branchdiff-resolve — AI reads open comments, fixes the code, resolves each thread

Say /branchdiff-review not "review the diff" — without the slash command, your AI may pick a different review tool by mistake.

Option B — Any AI: copy-paste prompts

The AI can run branchdiff review guide for review/resolve workflows, or branchdiff agent guide for the complete CLI reference covering all commands. The prompts below instruct the AI to start with review guide.

To review:

You are reviewing code using branchdiff agent commands (not any other tool).
Run `branchdiff review guide` first to load the full reference, then:
1. Run `branchdiff agent diff` to read the full diff.
2. Post inline comments: branchdiff agent comment --file <path> --line <n> --body "[tag] message"
   Tags: [must-fix] bugs/security · [suggestion] improvements · [nit] style · [question] unclear
3. For multi-line: add --end-line <n>. Diff-wide: branchdiff agent general-comment --body "..."
4. Confirm: branchdiff agent list --status open
Start: branchdiff review guide

To review a specific branch comparison (no session needed):

branchdiff review context --refs "main feature" | your-ai-tool

To resolve:

You are resolving open review comments using branchdiff agent commands.
Run `branchdiff review guide` first to load the full reference, then:
1. Run `branchdiff agent list --status open --json` to get open threads.
2. For each thread: fix the code, then:
   branchdiff agent resolve <id> --summary "what you did"
   branchdiff agent dismiss <id> --reason "why not fixing"
   branchdiff agent reply <id> --body "answer"  (for questions)
Start: branchdiff review guide

Option C — One-shot pipe

branchdiff review context | your-ai-tool
branchdiff review context --refs "main feature" | your-ai-tool   # no session needed
branchdiff review run --exec "claude -p 'review for security'" --mode review
branchdiff review run --exec "llm -m gpt-4o" --mode resolve

Option D — Load full guide (humans and AI)

branchdiff review guide    # review/resolve workflows
branchdiff agent guide     # complete AI agent reference (all commands)

Agent command reference

branchdiff agent diff                                         # read the full diff
branchdiff agent list --json                                  # all threads
branchdiff agent list --status open --json                    # only open threads
branchdiff agent comment \
  --file src/app.ts --line 42 \
  --body "[must-fix] Missing null check"                     # post inline comment
branchdiff agent comment \
  --file src/app.ts --line 42 --end-line 48 \
  --body "[suggestion] Extract this into a helper"           # multi-line range
branchdiff agent general-comment \
  --body "[suggestion] Overall: auth module needs attention" # diff-wide comment
branchdiff agent resolve <thread-id> --summary "Fixed"       # mark resolved
branchdiff agent dismiss <thread-id> --reason "By design"    # mark won't fix
branchdiff agent reply <thread-id> --body "Can you clarify?" # reply to thread
branchdiff agent delete-thread <thread-id>                   # delete thread + comments
branchdiff agent clear-threads                                # delete all threads
branchdiff agent edit-comment <id> --body "updated"          # edit a comment
branchdiff agent delete-comment <id>                          # delete a single comment

Notes:

• --file is relative to repo root (src/app.ts, not /Users/.../src/app.ts)
• --line is 1-indexed. --end-line defaults to --line if omitted
• Thread IDs accept 8-char prefix: abc123de instead of the full UUID

Severity tags

| Tag | Meaning | |---|---| | [must-fix] | Bug, security issue, data loss — must be fixed before merge | | [suggestion] | Improvement, not required | | [nit] | Style, naming, cosmetic | | [question] | Unclear behavior, needs clarification |

Workflow 1 — AI Review

You are reviewing a code diff using branchdiff.

1. Run `branchdiff agent diff` to read the full diff.
2. For each genuine issue, post a comment:
   branchdiff agent comment --file <path> --line <n> --body "[<tag>] <message>"
   Use [must-fix] for bugs/security, [suggestion] for improvements,
   [nit] for style, [question] for unclear behavior.
3. Be concrete: quote the problematic code or reference the exact line.
   Avoid generic advice — say which error, at which line, and what should change.
4. For multi-line issues add --end-line <n>.
   For diff-wide comments use `branchdiff agent general-comment`.
5. After posting, run `branchdiff agent list --status open` to confirm comments are clear.

Start: branchdiff agent diff

Workflow 2 — AI Resolve

You are resolving open review comments using branchdiff.

1. Run `branchdiff agent list --status open --json` to get open threads.
2. For each thread:
   - [must-fix] or [suggestion]: apply the fix, then resolve:
     branchdiff agent resolve <id> --summary "<what you did>"
   - [question]: answer with a reply instead:
     branchdiff agent reply <id> --body "<answer>"
   - Disagree: dismiss with a reason (don't silently skip):
     branchdiff agent dismiss <id> --reason "<why>"
   - [nit]: skip unless it's a one-line change
3. After all threads, run `branchdiff agent list --json` and report:
   how many resolved, replied, dismissed.

Start: branchdiff agent list --status open --json

Workflow 3 — AI Tour

You are creating a guided code tour using branchdiff.

Topic: <e.g. "How authentication works">

1. Start the tour:
   branchdiff agent tour-start --topic "<topic>" --body "<one-paragraph overview>" --json
   Record the returned tour id.
2. Add 5–12 steps in logical order:
   branchdiff agent tour-step --tour <id> \
     --file <path> --line <n> [--end-line <n>] \
     --body "<explain WHY this code exists, edge cases, related steps>" \
     --annotation "<short label on the highlighted region>"
3. Finish: branchdiff agent tour-done --tour <id>
4. Tell the user to view it in the branchdiff UI (Tour panel).

Start: branchdiff agent tour-start

Workflow 4 — AI Summary

Summarize the current branchdiff review session.

1. Run `branchdiff agent list --json` to get all threads.
2. Output:
   - One-sentence verdict (approve / changes requested / needs more eyes)
   - Top must-fix items (file:line + one-line reason each)
   - Any recurring themes ("three null-check comments" → suggest a lint rule)
   - Count: open / resolved / dismissed
3. Format as markdown, suitable for a PR description. Keep under 150 words.

Start: branchdiff agent list --json

Workflow 5 — Security Audit

You are doing a SECURITY-FOCUSED review using branchdiff.

1. Run `branchdiff agent diff` to see every changed line.
2. Look ONLY for security issues (skip style, perf, naming):
   - Injection: SQL, command, XSS, template, NoSQL, prompt
   - Auth/authz: missing checks, broken session logic, privilege escalation
   - Secrets: hardcoded keys/tokens, values leaked to logs
   - Crypto: MD5/SHA1 for passwords, weak RNG, hand-rolled crypto
   - Deserialization: eval/Function/pickle on untrusted input
   - Path traversal, SSRF, open redirect
   - Dependency risk: vulnerable ranges, typosquat names
3. For each finding:
   branchdiff agent comment --file <p> --line <n> \
     --body "[must-fix] <category>: <what, why it's exploitable, minimal fix>"
   Cite CWE where helpful (e.g. "CWE-89 SQL injection").
4. Zero findings is valid — say so:
   branchdiff agent general-comment \
     --body "[question] No security issues found. Checked: <what you reviewed>."

Start: branchdiff agent diff

Workflow 6 — Test Coverage Gaps

You are finding TEST COVERAGE gaps using branchdiff.

1. Run `branchdiff agent diff` to see additions.
2. For every new function, branch, or error path, check the test directory
   (e.g. **/*.test.ts, tests/**) for coverage.
3. For each uncovered path:
   branchdiff agent comment --file <p> --line <n> \
     --body "[suggestion] No test covers <path>. Suggested:
     describe('<fn>', () => { it('<case>', () => { ... }) })"
4. Priority: error branches > new public API > edge cases > happy path.
   Skip private helpers already exercised transitively.
5. Summarize: N new paths, M covered, K missing.
   branchdiff agent general-comment --body "<summary>"

Start: branchdiff agent diff

Workflow 7 — Breaking-Change Review

You are reviewing a BREAKING CHANGE using branchdiff.
Context: comparing <base-ref> → <new-ref>.

1. Run `branchdiff agent diff`.
2. Classify every change:
   BREAKING: removed exports, changed function signatures, renamed public types,
   removed CLI flags, changed HTTP endpoints, DB schema changes without migration.
   NON-BREAKING: additions, deprecations with shims, internal refactors.
3. For each BREAKING item:
   branchdiff agent comment --file <p> --line <n> \
     --body "[must-fix] BREAKING: <what changed> — callers must <action>.
     Migration: <concrete steps>."
4. Draft an UPGRADE.md snippet:
   branchdiff agent general-comment --body "<breaking changes + before/after + rollback notes>"
5. Flag any schema migration without a rollback path as [must-fix].

Start: branchdiff agent diff

Workflow 8 — Dependency Review

You are reviewing DEPENDENCY CHANGES using branchdiff.

1. Run `branchdiff agent diff` and focus on:
   package.json, pnpm-lock.yaml, yarn.lock, package-lock.json,
   and new import/require lines for added packages.
2. For every ADDED or MAJOR-BUMPED dependency check:
   - Maintained? (last publish < 1 year, reputable owner)
   - License compatible with the project?
   - Bundle size — is it imported in client code?
   - First-party alternative already in the repo?
   - Known CVEs (run npm audit if available)
3. For each finding:
   branchdiff agent comment --file package.json --line <n> \
     --body "[<severity>] <pkg>@<ver>: <risk>. Alternative: <x>."
   [must-fix] = abandoned / GPL in MIT project / critical CVE
   [suggestion] = large bundle / first-party alternative exists
   [question] = unclear why this was added
4. Summarize: added N, removed M, bundle-size delta, license concerns.
   branchdiff agent general-comment --body "<summary>"

Start: branchdiff agent diff

Tips

• Keep branchdiff running while the AI works. Agents hit http://localhost:<port>/api/*.
• Pass --json when the agent needs structured output.
• Short thread IDs work. First 8 chars of a UUID is enough: branchdiff agent resolve abc123de.
• Nothing leaves your machine. No telemetry, no cloud, no API key.
• Multiple sessions open? Run branchdiff agent diff | head -3 to confirm which branches the AI is reviewing.

Platform integrations

Sync review comments between branchdiff and GitHub PRs. Works for both AI-generated and manually posted comments.

Prerequisites

1. Install the GitHub CLI: gh --version
2. Authenticate: gh auth login
3. Your repo's git remote must point to github.com
4. A PR must be open for your current branch (or use a PR URL: branchdiff https://github.com/owner/repo/pull/123)

Push local comments to GitHub

When branchdiff detects an open PR, a GitHub button appears in the toolbar showing the PR number — for example, if your PR is #42, the button shows #42. Click it to open the sync dialog.

1. Write comments in branchdiff (manually or via AI review)
2. Click the PR number button in the toolbar (e.g. #42)
3. Click Push to PR — each single-comment thread is posted as an inline review comment on the GitHub PR
4. You'll see a toast showing how many were pushed, skipped (duplicates), or failed

Only single-comment threads can be pushed. Threads with replies are skipped — GitHub's review comment API doesn't map cleanly to multi-reply threads.

Pull GitHub comments into branchdiff

1. Click the #42 button in the toolbar
2. Click Pull from PR — all review comments from the GitHub PR are imported as local threads
3. Duplicate comments (same file, line, and body) are automatically skipped

Requirements for sync

• Your local HEAD must match the PR's head commit (push/pull git changes first)
• No uncommitted changes in your working tree (commit or stash first)

Prerequisites

Option A — Bitbucket App Password (recommended)

1. Go to bitbucket.org/account/settings/app-passwords → Create app password
2. Enable scopes: Repositories: Read + Pull requests: Read + Pull requests: Write
3. Set BITBUCKET_USERNAME to your Bitbucket username (shown at bitbucket.org/account/settings/)

Option B — Atlassian API Token

1. Go to id.atlassian.com → Security → API tokens → Create API token
2. Set BITBUCKET_USERNAME to your email address (not Bitbucket username) — Atlassian tokens use email for auth

Important: App Password uses Bitbucket username; Atlassian API Token uses email. Mixing these causes 401.

Set credentials after creating the token:

# Environment variables (restart branchdiff after setting)
export BITBUCKET_USERNAME="your-username-or-email"
export BITBUCKET_API_TOKEN="your-token"

# Config file (more convenient — no restart needed on next run)
mkdir -p ~/.branchdiff
echo '{"bitbucket":{"username":"your-username-or-email","apiToken":"your-token"}}' > ~/.branchdiff/credentials.json
chmod 600 ~/.branchdiff/credentials.json

5. Your repo's git remote must point to bitbucket.org
6. A PR must be open for your current branch

NOTE: Push and pull work identically to GitHub — click the PR number button in the toolbar (e.g. #42).

Usage Guide

| I want to… | Command | |---|---| | See uncommitted changes | branchdiff | | Compare with main (or any base) | branchdiff main | | Compare two branches | branchdiff main feat | | View a GitHub PR | branchdiff https://github.com/owner/repo/pull/123 | | Browse repo files | branchdiff tree | | View last N commits | branchdiff HEAD~3 | | Compare branch vs parent | branchdiff -p | | Compare branch vs 3rd commit back | branchdiff -p 3 | | Only unstaged changes | branchdiff -p 0 | | Re-open a running instance | branchdiff open | | Stop all instances | branchdiff kill | | Self-update | branchdiff update | | Check version | branchdiff version | | Show repo info & state | branchdiff info | | View user guide (no repo needed) | branchdiff guide | | View release changelog (no repo needed) | branchdiff changelog |

Viewing diffs

My uncommitted changes

branchdiff              # unstaged + staged
branchdiff staged       # only staged
branchdiff unstaged     # only unstaged

Recent commits

branchdiff HEAD~1       # last commit
branchdiff HEAD~5       # last 5 commits

Comparing branches or refs

branchdiff main                 # main vs. current branch
branchdiff main feat            # two branches
branchdiff main..feat           # range syntax (same result)
branchdiff v1.0.0 v2.0.0        # tags
branchdiff 1df74cc 3b9a54d      # commit SHAs
branchdiff origin/main feat     # remote + local

Anything git rev-parse --verify accepts works.

Viewing a GitHub PR

branchdiff https://github.com/owner/repo/pull/123

Requires gh CLI installed and authenticated (gh auth login).

Review sessions

branchdiff tracks inline comments in a local SQLite database. How sessions work depends on what you're comparing:

Branch comparisons — persistent

When comparing two named branches, tags, or remote branches, your review comments persist across new commits. Reopening the same comparison always shows previous comments — just like a GitHub PR thread.

branchdiff main..feature     # comments survive new commits to either branch

To start a fresh review (archive current comments and begin empty):

branchdiff main..feature --new          # archive + restart
# or: click "New review" in the browser toolbar

Archived comments are preserved and accessible:

branchdiff review threads --session <id>   # view archived session

Snapshot reviews — ephemeral

Working tree, staged changes, or a specific commit get their own session per HEAD state. Making a new commit creates a new session — old comments are not shown.

Summary

| Comparison type | Comments survive new commits? | Start fresh | |---|---|---| | branchdiff main..feature | Yes | --new or "New review" button | | branchdiff HEAD~1 | No — new commit = new session | — | | branchdiff (working tree) | No — new commit = new session | — |

Diff modes

Git mode (default)

Standard git diff branch1..branch2 — compares commit ancestry.

branchdiff main feat            # git mode is the default
branchdiff main feat --mode git

File mode

Compares actual file content (blob hashes) at each branch tip, ignoring commit history. Use when branches may have converged via rebase/cherry-pick.

branchdiff main feat --mode file

Example: both branches added the same line via different commits.

• File mode → no change (content is identical)
• Git mode → modified (commit paths differ)

Delta mode (Δ) — browser only

Toolbar button. Shows what the two modes disagree on:

• Git-only (amber) — appears in git diff but not file diff
• File-only (blue) — appears in file diff but not git diff
• Shared — both modes agree

Options

| Flag | Description | |---|---| | --mode <file\|git> | Diff mode (default: git) | | --port <n> | Port (default: auto-assigns from 5391) | | --no-open | Don't auto-open browser | | --dark | Dark theme | | --unified | Unified view (default is split) | | --quiet | Minimal terminal output | | --new | Archive current session and start fresh | | -p, --previous [n] | Compare branch against Nth previous commit (default: 1). Use -p 0 for unstaged-only view |

Instance management

Multiple repos open at once — each gets its own port starting at 5391.

branchdiff list         # show all running instances
branchdiff open         # reopen browser for this repo (prompts to choose if multiple running sessions)
branchdiff kill         # stop all instances
branchdiff prune        # delete all stored data (~/.branchdiff)
branchdiff clear        # reset current repo's review data
branchdiff doctor       # diagnose install / environment issues
branchdiff update       # self-update (auto-detects package manager)
branchdiff version      # print current version
branchdiff version --check  # check for updates
branchdiff info         # show repo fingerprint and state table size
branchdiff state reset  # clear UI state without affecting sessions
branchdiff guide        # open user guide in browser (no repo required)
branchdiff changelog    # open release notes in browser (no repo required)

PR, sync & session commands

Manage pull requests, sync comments, and control sessions from the terminal. All commands target a running branchdiff instance (supports --port/--pid for multi-instance environments).

branchdiff pr info                              # show PR status
branchdiff pr create --title "Fix" --source feat --dest main
branchdiff pr merge --strategy squash           # merge, squash, or rebase
branchdiff pr approve --comment "LGTM"          # approve the PR
branchdiff pr request-changes --comment "Fix X"
branchdiff pr close / reopen / draft / ready
branchdiff pr edit --title "New title"          # edit PR title or body
branchdiff pr comment --body "Nice work"        # add a general comment
branchdiff sync push                            # push local threads → remote PR
branchdiff sync pull                            # pull remote comments → local session
branchdiff session current                      # show active session
branchdiff session archive                      # archive current session
branchdiff session history                      # list archived sessions
branchdiff session delete --id <id>             # delete an archived session

Rerunning branchdiff in a repo that already has a running instance reuses it (just reopens the browser). Use --new to force a restart.

Data & privacy

Everything is local. No outbound calls except:

• localhost (UI ↔ CLI server)
• GitHub API via your local gh CLI (only for PR viewing and comment sync — only when you click a sync button)

Stored in ~/.branchdiff/:

• registry.json — running instance metadata
• <repo-hash>/ — per-repo SQLite with comment threads

Wipe everything: branchdiff prune

Troubleshooting

"Not a git repository" — run from inside a git working tree.

Port already in use — use branchdiff --port 7000.

UI won't load / stale state — run branchdiff --new.

Native module errors (better-sqlite3) — happens after switching Node versions:

npm rebuild -g better-sqlite3

"GitHub CLI (gh) is not installed" — install from https://cli.github.com then gh auth login.

Something else — run branchdiff doctor.

Uninstall

npm uninstall -g @encryptioner/branchdiff
branchdiff prune          # or: rm -rf ~/.branchdiff

Keyboard Shortcuts

| Key | Action | |---|---| | j / k | Next / previous file | | n / p | Next / previous hunk | | Shift+X | Collapse / expand all | | ? | Show all shortcuts |

Why branchdiff?

Standard git diff compares commit ancestry — it can show a "change" when both branches actually contain identical content (just via different commits). branchdiff's file mode compares actual file content at each branch tip.

main:  A → B → C → D   (file.js = "hello world")
feat:  A → X → Y       (file.js = "hello world")

git diff main..feat  →  shows diff  (different commit paths)
branchdiff main feat →  no diff     (same content)

Switch between modes in the browser toolbar, or use --mode file / --mode git.

Features

• Syntax highlighting (150+ languages), split and unified views
• Inline comments with severity tags ([must-fix], [suggestion], [nit], [question])
• Markdown preview in comment editor — toggle between Write and Preview before posting
• Persistent review sessions — comments survive new commits when comparing named branches
• Full view mode — VS Code-style side-by-side full file view with inline comments and scroll markers
• Delta mode (Δ) — highlights what each diff mode reports differently
• Sidebar filtering — filter files by 9 states: Commented, Uncommented, Viewed, Unviewed, Stale, Collapsed, Expanded, Staged, Unstaged
• File status indicators — inline badges on file rows: S (staged), U (unstaged), amber dot (stale), checkmark (viewed)
• Stale viewed detection — viewed files auto-flagged when content changes (FNV-1a hash)
• UI state persistence — collapse state, viewed markers, and preferences persist across ports and machines
• Working tree toggle — switch between staged and unstaged changes from the toolbar
• GitHub & Bitbucket PR integration — push/pull review comments, create PRs from the UI
• CLI commands for PR, sync & session — manage PRs, sync comments, and control sessions from the terminal (branchdiff pr, branchdiff sync, branchdiff session)
• Multiple repos open simultaneously on different ports
• 100% local — no telemetry, no cloud, no API key

Guideline

View the complete user guide and command reference:

• Online: encryptioner.github.io/branchdiff-releases/guideline.html
• After installation: Run branchdiff guide (opens at http://localhost:<port>/guideline)
• Workflows included: AI review, resolve, tour creation, security audit, test coverage, breaking changes, dependency review, PR summary

Changelog

View the release history and what's changed:

• Online: encryptioner.github.io/branchdiff-releases/changelog.html
• After installation: Run branchdiff changelog (opens at http://localhost:<port>/changelog)

License

Commons Clause + MIT — see LICENSE.md (browse via npm code tab) for full text.

Contributing

Feedback and bug reports are welcome on the GitHub repo. More projects by the author: github.com/Encryptioner. His portfolio: encryptioner.github.io.

If you find branchdiff useful, consider giving it a star on GitHub!

Support

If branchdiff saves you time, consider supporting its development:

Acknowledgments

Inspired by Diffity