Twitter/X

Indexing once cuts agent context dramatically

2026-07-31 · 05:10 UTC ·@om_patel5 ·1 min read

Brief

The tool indexes a repository and keeps it current on every commit, letting agents read indexed answers instead of re-parsing code; it reduces per-commit context from 64,000 to 2,400 tokens (up to 96% reduction) and adds a 16-language dependency graph, file-level code-health scores, concrete refactor suggestions, git-history validation, and auto-generated claude.md/agents.md.

Why it matters

Indexing once cuts agent context dramatically: loading one commit’s context drops from 64,000 tokens to 2,400 (up to 96% fewer tokens), with 89% fewer file reads and 70% fewer tool calls.

Key details

  • Per-file analysis includes a dependency graph across 16 languages, a code-health score from 25 markers computed in under 30 seconds on a 3,000-file repo, and concrete fix recommendations (move method, split file, break cycle) with blast-radius estimates.
  • The tool validates flags against git history (example: 17 of the 20 lowest-health files had bug fixes in the last 6 months, 3.6x the baseline), auto-generates claude.md and agents.md, reads agent transcripts, is free/open-source, runs locally, and has ~4,300 stars and ~60,000 downloads.
Source evidence

THIS GUY BUILT A TOOL THAT CUTS UP TO 96% OF THE TOKENS YOUR AI AGENT BURNS JUST FIGURING OUT YOUR CODEBASE

right now your agent rediscovers your repo from scratch on every single task. grep, read, re-read, forget, repeat. most of its budget goes to working out where things are before it writes a single line

this indexes the whole thing once and keeps it current on every commit, so the agent reads the answer instead of the codebase

> loading one commits context drops from 64,000 tokens to 2,400
> up to 96% fewer tokens to load context, 89% fewer file reads, 70% fewer tool calls
> it builds a dependency graph across 16 languages, so the agent knows what calls what and what breaks if you change it
> it reads your git history for hotspots, hidden coupling between files, ownership and which files actually keep getting bug fixed
> a code health score on every file from 25 markers, no llm, under 30 seconds on a 3,000 file repo
> it names the actual fix, not just "this file is risky", but move this method, split this file, break this cycle, with the blast radius attached
> it auto generates your claude.md and agents.md from the real index
> it even reads your own agent transcripts for corrections you keep repeating and turns them into tracked decisions it feeds back later

it also validates itself against your own git history. after indexing it checks its own flags and tells you something like "17 of the 20 lowest health files had a bug fix in the last 6 months, 3.6x the baseline"

so if its wrong on your repo, you see it immediately

its free, open source, runs entirely on your machine, and its already at 4,300 stars and 60,000 downloads which is insane

Video