Skip to main content

diffctx — smart diff context for LLM code review

CI PyPI crates.io npm License

diffctx selects the minimum code an LLM needs to review a git diff. Instead of pasting whole files, it walks the dependency graph outward from the changed lines and stops once more context stops paying for itself.

Formerly published as treemapper — every command, flag, and API call works unchanged.

How it compares

Whole-repo packers (repomix and friends) seed on the repository and export everything; persistent code-graph servers answer structural queries against a maintained index. diffctx is diff-seeded: the input is a change, the output is the fragments needed to understand it, packed under a hard token budget — local, deterministic, no index, no model calls. Measured results and when the other two families fit better: COMPARISON.md.

Install

uvx diffctx . --diff HEAD~1             # zero-install, run once via uv
pipx install diffctx                    # recommended: isolated CLI, no venv needed
pip install diffctx                     # or: into an active environment
pipx install 'diffctx[mcp]'             # + MCP server for AI assistants

Without Python:

cargo install diffctx                   # native CLI from crates.io
npx diffctx . --diff HEAD~1             # npm wrapper over the native binary
docker run --rm -v "$PWD:/repo" ghcr.io/nikolay-e/diffctx . --diff HEAD~1

On Windows, via Scoop (this repository is the bucket):

scoop bucket add diffctx https://github.com/nikolay-e/diffctx
scoop install diffctx/diffctx

Prebuilt binaries for linux (x86_64/aarch64), macOS (arm64) and Windows (x64) are attached to every release. The native binary and Docker image cover diff mode with YAML/JSON output and write to stdout (redirect to capture); tree mode, Markdown output, the graph subcommand and the MCP server live in the Python package.

Quick start

diffctx . --diff HEAD~1       # smart context for last commit → paste into Claude/ChatGPT
diffctx . -f md -c            # full codebase export → clipboard in Markdown

diffctx demo

diffctx . --diff HEAD~1 selects only the fragments an LLM needs to review the last commit, instead of dumping every changed file in full.

Diff context mode

Finds the minimal set of fragments needed to understand a change — imports, callers, type definitions, config dependencies — across 50+ file types. It builds a code graph (imports, co-changes, type refs), propagates relevance outward from the changed lines, and stops when relevance drops below --tau or the --budget token cap is hit.

--diff takes a git range (HEAD~1..HEAD, main..feature) or a duration window ending now — 24h, 8d, 90min, 1h30m, 2w (units s, m/min, h, d, w, composable). A window diffs the working tree against the last commit before it, so it covers the commits made inside the window plus the uncommitted and untracked work on top — diffctx . --diff 24h is "everything I touched today". A ref that happens to look like a duration (a branch 24h) keeps its git meaning.

Flag Default Description
--scoring ego ego = bounded expansion around changed nodes (fast, predictable radius); ppr = Personalized PageRank (global, smoother decay, slower); bm25 = lexical retrieval against the diff hunks (baseline for sparse graphs); rrf = reciprocal-rank fusion of ego and bm25 (widest recall, no scale calibration between the two signals); pit = the same fusion on score percentiles
--budget auto Cap in o200k_base tokens on the whole rendered artifact (see Token counting): every changed file gets one witness first, relevance fills the rest, and the renderer drops context from the tail until the document fits. A budget smaller than the summary yields the summary alone. N = fixed cap, -1 disables it, 0 is a strict-zero floor (no fragments; use --full for changed files only)
--alpha 0.60 PPR continuation probability: higher = relevance travels further from the change, lower = tighter around it (--scoring ppr only)
--tau 0.05 Relevance threshold for full fragment content; lower-scoring fragments are stubbed or dropped (lower = more context)
--full false Only the changed files, every fragment, no related-code context
--timeout 300 Wall-clock deadline in seconds; on expiry the run stops cooperatively and emits a partial artifact whose coverage block names the limit (exit 0). 124 is the watchdog behind it, 30 s later, for a phase that could not stop
--with-raw-diff false Also embed git's raw unified diff ahead of the selected fragments — additive (selection unchanged), not charged to --budget, lock/ignored/secret-like sections omitted. Python CLI only
--mode pack locate emits the same ranked selection as compact diffctx.locate.v1 JSON — path, lines, score, provenance reasons, a blast-radius summary and per-item impact group (test/type/config), NO source bodies. Adds a coverage block naming what the run could not see (unparsed_files, zero_edge_files, ppr_truncated, next_up, a heuristic confidence) and an overflow ranking of what the budget left behind — omitted entirely when there is nothing to disclose. diffctx . --diff --mode locate = impact of your uncommitted change. The MCP tool takes it as mode="locate"

Every JSON/YAML artifact opens with schema: diffctx.context.v1 and validates against schemas/diffctx.context.v1.json, generated from the engine's own type; it closes with a provenance block (engine version, input object ids, the effective configuration and its hash, the selection parameters, the tokenizer) and, when a limit stopped the run short, a coverage block naming it.

graph subcommand

Explore the underlying dependency graph directly, without a diff:

diffctx graph .                                  # Mermaid graph of directory deps (default)
diffctx graph . --summary                        # cycles, hotspots, coupling metrics
diffctx graph . --level fragment -f json         # fragment-level graph as JSON
diffctx graph . --level file -f graphml -o g.xml # file-level graph as GraphML

Usage

# full codebase export:
diffctx .                                 # Markdown to stdout + token count
diffctx . -f md -c                        # Markdown → clipboard
diffctx . -f json -o tree.json            # JSON → file
diffctx . --no-content                    # structure only, no file contents
diffctx . --max-depth 3                   # limit depth
diffctx . -i custom.ignore                # custom ignore patterns

# diff context mode (requires git repo):
diffctx . --diff                          # uncommitted changes (working tree vs HEAD)
diffctx . --diff HEAD~1                   # context for last commit
diffctx . --diff main..feature            # context for feature branch
diffctx . --diff 24h                      # everything changed in the last 24 hours
diffctx . --diff 8d                       # same over 8 days (also 90s, 10min, 1h30m, 2w)
diffctx . --diff HEAD~1 --budget 30000    # limit to ~30k tokens
diffctx . --diff HEAD~1 -c                # diff context to clipboard
diffctx . --diff HEAD~1 --with-raw-diff   # raw patch + selected context
diffctx . --diff HEAD~1 --mode locate     # ranked navigation JSON, no source

Every run reports token count and size on stderr — 12,847 tokens (o200k_base), 52.3 KB. Counts are exact only for the GPT-4o family; Claude, Gemini and others tokenize differently, so treat --budget as an upper bound and leave headroom (details). Unreadable files become placeholders like <binary file: N bytes>.

Python API

from pathlib import Path
from diffctx import build_diff_context, map_directory, to_json, to_markdown, to_text, to_yaml

ctx = build_diff_context(
    Path("."),
    "HEAD~1..HEAD",
    budget_tokens=None,       # None = auto; 0 = no fragments; -1 = uncapped; N = cap on the whole artifact
    alpha=0.6,
    tau=0.05,
    full=False,
    scoring_mode="ego",
    timeout=300,
    with_raw_diff=False,      # True also embeds the raw unified diff (not charged to budget)
)
print(to_markdown(ctx))

tree = map_directory(
    ".",
    max_depth=None,
    no_content=False,
    max_file_bytes=None,
    ignore_file=None,
    no_default_ignores=False,
    whitelist_file=None,
)
print(to_yaml(tree))

MCP server

MCP Registry diffctx MCP server

diffctx includes an MCP server that lets AI assistants (Claude Code, Cursor, Windsurf, etc.) call diff context analysis automatically during code review. It is published in the official MCP registry as io.github.nikolay-e/diffctx. One-line setup (zero-install via uv):

# Claude Code
claude mcp add diffctx -- uvx --from 'diffctx[mcp]' diffctx-mcp
# Codex CLI
codex mcp add diffctx -- uvx --from 'diffctx[mcp]' diffctx-mcp
# Gemini CLI
gemini mcp add diffctx uvx -- --from 'diffctx[mcp]' diffctx-mcp
# VS Code
code --add-mcp '{"name":"diffctx","command":"uvx","args":["--from","diffctx[mcp]","diffctx-mcp"]}'

With pip install 'diffctx[mcp]' already done, replace the uvx --from 'diffctx[mcp]' diffctx-mcp tail with plain diffctx-mcp.

The server exposes one tool, diffctx_context, that assistants call when reviewing PRs, explaining changes, or investigating broken tests. It ranks the code that explains a diff, then reads only the fragments the assistant picked — two calls that pay for the selection instead of a whole pack. The wider get_tree_map and get_file_context tools are opt-in via DIFFCTX_MCP_LEGACY_TOOLS=1. Filesystem confinement via DIFFCTX_ALLOWED_PATHS: see SECURITY.md.

Every stdio client takes the same server shape; only the config file differs:

Client Config file Key
Claude Code (project) .mcp.json mcpServers
Claude Desktop claude_desktop_config.json mcpServers
Cursor ~/.cursor/mcp.json mcpServers
Windsurf ~/.codeium/windsurf/mcp_config.json mcpServers
Continue ~/.continue/config.json experimental.modelContextProtocolServers (transport object)
Zed ~/.config/zed/settings.json context_servers (command.path)
{
  "mcpServers": {
    "diffctx": {
      "command": "uvx",
      "args": ["--from", "diffctx[mcp]", "diffctx-mcp"]
    }
  }
}

With pip install 'diffctx[mcp]' already done, "command": "diffctx-mcp" with no args works everywhere instead. Use the diffctx-mcp entry point, not the diffctx mcp subcommand: the latter only exists from 1.12.3 onward and would map a directory named mcp on older releases.

Ignore patterns

Respects .gitignore and .diffctx/ignore automatically — hierarchically at every directory level, with full gitignore semantics (negation !important.log, anchored /root_only.txt), and the output file is always auto-ignored. Three controls are tree mode only and are refused with --diff: .diffctx/whitelist (-w) as an include-only filter, -i for an extra ignore file, and --no-default-ignores / --no-ignores to drop the built-in patterns or every ignore rule.

An excluded path never appears in the output in any role: in diff mode it is dropped both from changed_files and from the candidate universe, so it cannot come back as a related-context fragment either (including under --full). The same guarantee covers secret-like paths (id_rsa, *.pem, *.key, ...), which are filtered even without an ignore entry.

Token cache

Diff mode caches per-blob tokenization in the OS cache directory (e.g. ~/Library/Caches/diffctx/token-cache) — a pure speedup, safe to delete. DIFFCTX_TOKEN_CACHE_DIR relocates it; DIFFCTX_TOKEN_CACHE_MAX_BYTES caps its size (default 512 MB, 0 disables eviction).

Exit codes

Code Meaning
0 Success — output contains content
1 Runtime error (bad path, permission denied, etc.)
2 Usage error (invalid flags/arguments)
3 Environment error (--diff outside a git repo, git not installed, no commits yet)
4 --diff produced no semantic context (clean tree, binary-only, everything filtered); output is still emitted. Deletion/rename/lockfile-only diffs list deleted_files/renamed_files/lockfile_changes and exit 0
124 --diff ran 30 s past the --timeout deadline without stopping cooperatively (the deadline itself yields a partial artifact and exit 0)
130 Interrupted (Ctrl-C)
141 Broken pipe (e.g. piping into head)

License

Apache 2.0


  • Documentation site — the pipeline end to end: diff → fragments → graph → relevance → selection
  • Command-line reference — every flag with its default and meaning, rendered from diffctx --help
  • GitHub Action — diff context as a CI step for LLM review
  • Token counting — which encoder, and what --budget means for non-GPT models
  • Comparison — measured results, and when a whole-repo packer or a persistent code-graph server fits better
  • Benchmarks — every published number with what it was measured on, and how to reproduce it
  • FAQ — heuristic or oracle, whose tokens, monorepos, the raw diff, secrets
  • Paper — budgeted typed-graph retrieval for diff-aware context selection (Zenodo, 2026)
  • Changelog
  • Security policy — threat model and vulnerability reporting
  • Parameter strategy — how --alpha, --tau, and edge weights are calibrated

Metadata

Release files for diffctx 1.16.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for diffctx 1.16.0
File Size Uploaded
diffctx-1.16.0.tar.gz 476.0 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for diffctx 1.16.0
File
diffctx-1.16.0-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details
diffctx-1.16.0-cp310-abi3-manylinux_2_28_x86_64.whl CPython 3.10 abi3 Linux glibc 2.28+ x86-64 Details
diffctx-1.16.0-cp310-abi3-manylinux_2_28_aarch64.whl CPython 3.10 abi3 Linux glibc 2.28+ ARM64 Details
diffctx-1.16.0-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details

Total release size: 37.4 MB

Release files / diffctx-1.16.0.tar.gz

Download URL diffctx-1.16.0.tar.gz
Size 476.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2b4f1a93d24469de2c910f501880df0d6fecffe1c1dc80c38b02d68476889dd4
BLAKE2b-256 checksum
How to use checksums
f0085aeb7c156a2477795edc7065c88eaf52134bd478025311d4f33d451b0fef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release files / diffctx-1.16.0-cp310-abi3-win_amd64.whl

Download URL diffctx-1.16.0-cp310-abi3-win_amd64.whl
Size 9.3 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
a317ff040d3d07a0683f9c8bfae74c577076f0c56fed92c20d8ec130b28f089f
BLAKE2b-256 checksum
How to use checksums
6edf216c7e1e5144fcccf4add5b660db4517be16b93489cb58c9c4b49efbd2d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release files / diffctx-1.16.0-cp310-abi3-manylinux_2_28_x86_64.whl

Download URL diffctx-1.16.0-cp310-abi3-manylinux_2_28_x86_64.whl
Size 9.3 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
e96a2d48d6e059e90e40bc0c1227408721dceef7aecfacc3c40e676580d732c9
BLAKE2b-256 checksum
How to use checksums
62de829e92a1c1a38c8109abf11cb983df1a68c78de32372d277ba4dd32549cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release files / diffctx-1.16.0-cp310-abi3-manylinux_2_28_aarch64.whl

Download URL diffctx-1.16.0-cp310-abi3-manylinux_2_28_aarch64.whl
Size 9.0 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
dd4bb974f9f49b09ea0878f2b223ef2e3a6551ab78ee270214342c613603e8c2
BLAKE2b-256 checksum
How to use checksums
403f543b0409d1c9e8b9a1a26e64c6e8dc301c9eedb4be55fafc094718130219
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log

Release files / diffctx-1.16.0-cp310-abi3-macosx_11_0_arm64.whl

Download URL diffctx-1.16.0-cp310-abi3-macosx_11_0_arm64.whl
Size 9.3 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
e95e2a084688f3d53584f420bd2e8e23891043fe7bff7900403e48af52e7fde3
BLAKE2b-256 checksum
How to use checksums
225ec68633693ad6e20e2490c9ad77635f0f116663b7732be73fde1851709eea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page