Red Hat's Ripwire Cuts Coding Agent Token Use by 96% Without Embeddings

Red Hat's ripwire is a zero-dependency C++23 CLI that hands coding agents a ranked, deterministic map of any repo without embeddings or vector DBs.

·
·
Red Hat's Ripwire Cuts Coding Agent Token Use by 96% Without EmbeddingsPRO
  • Red Hat released ripwire, a C++23 CLI that gives coding agents a ranked call graph of any repo.
  • Zero runtime dependencies, no embeddings, no vector DB, no index server, tree-sitter parses 16 languages.
  • Beat repowise 58.3% vs 33.3% strict file@10 on LocBench at 0.114s warm median.
  • Signatures cut element bytes 67% at top-50; whole-question bundles measured 24.9x token reduction on private corpus.
  • MCP server exposes 30 verbs to Claude, Cursor, Codex, Windsurf, Gemini, and Aider.
  • Ships with 17 task-shaped skills and publishes its own failure modes alongside wins.

Red Hat's Emerging Technologies group has released ripwire, a command-line tool that gives coding agents structural context on any repository in tens of milliseconds, with no embeddings, vector databases, or index server required. It parses your tree, builds a ranked call graph, and streams a deterministic XML map to stdout that a model can pull through an MCP server mid-task.

Ripwire is a zero-runtime-dependency C++23 binary. It crawls a repository tree, extracts symbols with tree-sitter, resolves references into a call graph, ranks that graph with Personalized PageRank, and streams minified XML to stdout. Two runs over the same tree produce byte-identical output, and warm runs match cold ones, enforced by CI on every push.

Why agents burn tokens on cold repos

When an agent lands in an unfamiliar repository, it typically greps for a keyword, opens files, follows imports, and spends tokens reconstructing structure the compiler already knows. Ripwire answers structural questions in tens of milliseconds from a warm index and labels every count it cannot prove is a total. Instead of shipping whole file bodies into context, an agent asks for callers, callees, blast radius, or the tests that need to run, and gets back a ranked list of symbols with paths and line numbers.

Ripwire dependency graph visualization

Token savings come from replacing full source with signature skeletons. On its own repository, --pack-signatures

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Comments

avatar