trigrep is an indexed regex search tool for large codebases, written in Rust.

Instead of scanning every file on each search like grep or ripgrep, trigrep builds a local, disk-backed trigram index of your repository. At query time it:

• decomposes your regex into literal fragments,
• turns them into trigrams (and later sparse n-grams),
• uses an inverted index to find only the small set of candidate files,
• then runs a real regex engine just on those candidates.

This keeps search latency almost flat even as your monorepo grows, and makes trigrep especially useful for AI coding agents and humans who search a lot in very large trees.

Based on the approach described in Cursor's Fast regex search: indexing text for agent tools.

In a real search-only benchmark on git.git, trigrep had the lowest mean query time: 0.0405s vs 0.0640s for ripgrep and 0.5990s for grep (~1.58x faster than ripgrep and ~14.79x faster than grep for this workload).

- Timestamp (UTC): 2026-03-23T18:01:22Z
- Source repo: /tmp/trigrep-bench/git
- Source commit: 6e8d538aab8fe4dd07ba9fb87b5c7edcfa5706ad
- Runs per pattern: 5
- Warmup runs per pattern: 1
- Patterns: TODO|FIXME, ^#include, struct [A-Za-z_][A-Za-z0-9_]*, parse
- Scope: search-only (trigrep index built once before timing)

# Latest release
curl -fsSL https://raw.githubusercontent.com/PythonicNinja/trigrep/master/scripts/install.sh | bash

# Pin a specific release
TRIGREP_VERSION=v0.1.2 curl -fsSL https://raw.githubusercontent.com/PythonicNinja/trigrep/master/scripts/install.sh | bash

Installer behavior:

• default version: latest GitHub release
• default install path: /usr/local/bin if writable, otherwise ~/.local/bin
• verifies SHA256 using release checksums.txt when available (new releases)

Installer variables:

Windows:

• download the matching .zip from GitHub Releases
• extract trigrep.exe and place it in a directory on your PATH

# From source
git clone git@github.com:PythonicNinja/trigrep.git && cd trigrep
make install

# Or build without installing
make build

The binary is installed to ~/.cargo/bin/trigrep.

Pushing a version tag (for example v0.1.2) triggers the release workflow in .github/workflows/release.yml. It builds trigrep for Linux, macOS, and Windows, packages binaries, generates checksums.txt, and publishes a GitHub Release with those assets.

Before tagging, bump the project version in all key places:

make version NEW_VERSION=0.1.1

Current release targets:

• x86_64-unknown-linux-gnu
• aarch64-unknown-linux-gnu
• x86_64-apple-darwin
• aarch64-apple-darwin
• x86_64-pc-windows-msvc

git tag v0.1.2
git push origin v0.1.2

# Build the index for your repo
trigrep index .

# Search with a regex
trigrep search "fn main" .

# Check index status
trigrep status .

Use make benchmark to compare grep, ripgrep, and trigrep and get a Markdown table with timing stats.

# Default: clones git.git into /tmp/trigrep-bench/git and benchmarks search time
make benchmark

# Benchmark any local repository
make benchmark BENCH_REPO_PATH=/path/to/repo

The benchmark writes Markdown to /tmp/trigrep-bench/benchmark.md by default and also prints it to stdout.

Build or rebuild the trigram index. Creates a .trigrep/ directory at the target path.

trigrep index .              # index current directory
trigrep index /path/to/repo  # index a specific repo
trigrep index . --force      # force rebuild

Search for a regex pattern using the index. If no index exists, one is built automatically.

trigrep search "pattern" .
trigrep search "fn\s+\w+" .          # regex supported
trigrep search "TODO|FIXME" .        # alternations
trigrep search "error" . -i          # case-insensitive
trigrep search "MyStruct" . -l       # files only
trigrep search "fn main" . -c        # count matches per file
trigrep search "pattern" . -w        # whole word
trigrep search "pattern" . --json    # JSON output
trigrep search "pattern" . --stats   # show index hit stats
trigrep search "pattern" . --no-index  # skip index, brute-force scan

Flags:

Show index metadata and staleness check against current git HEAD.

trigrep status .

1. Indexing: trigrep walks your repo (respecting .gitignore), extracts every overlapping 3-byte trigram from each text file, and writes an inverted index to .trigrep/ on disk.

2. Querying: Your regex is parsed and decomposed into literal fragments. These fragments are converted to trigrams and looked up via binary search in the mmap'd index. Posting lists are intersected (AND) or unioned (OR) to find candidate files. Only those candidates are scanned with the real regex engine.

See algorithm.md for full technical details.

Default output is grep-compatible:

src/main.rs:42:fn trigram_hash(a: u8, b: u8, c: u8) -> u32 {

JSON mode (--json):

{"file":"src/main.rs","line":42,"content":"fn trigram_hash(a: u8, b: u8, c: u8) -> u32 {"}

trigrep/
├── trigrep-index/   # Library: index building, reading, querying
└── trigrep-cli/     # Binary: CLI, regex decomposition, output formatting