CodeNib

Understand unfamiliar code with evidence. Read a Wiki of how a repository works, follow its call paths on a map, and open the source behind every explanation. Then give your coding agent the same index. Browse a Wiki · Use with your agent · Docs · Languages · Releases

The Requests Wiki . Each node on the map is a page, and the heavy lines are references the code index recorded between areas. The page cites a file and line range for each claim.

New in 0.2.6: Wikis open as a map of their pages and lead with the main path through the code, faster graph builds, and first C/C++ and JavaScript/TypeScript builds that leave the checkout alone. Read the release notes. A Wiki you can follow down to the source

CodeNib indexes a repository, groups its code into areas, and writes a Wiki page for each one. The map and the call paths come from the code index, so you can check every arrow against the source. Start from the map. Pages are nodes. Drag to pan, scroll to zoom, and click a node to read its page. Click a heavy line to read an example of the references behind it. Follow one path through the code. The Overview opens on the main path through the repository, one sentence per recorded call. The most important detail pages draw their longest recorded call path. No model chooses the arrows. Check each claim. Sentences end with the file and line range they come from, and each page lists its callers and calls in the code graph. Ask a follow-up. *Ask this repository* answers a question with source citations, using the model you configure.

The gin Wiki opens on one recorded path, from GET() to node.insertChild() . Open a Wiki To build a Wiki with the map on your machine:

This builds a search index and a symbol graph, then opens the Wiki at http://localhost:3000. Pages are written from the index without a model. Add --generate --model for model-written pages. Local Wiki guide

Use it with your coding agent

Build the same index for Claude Code or Codex. Your agent can then find definitions, follow callers and read the source in your own checkout.

One recorded Claude Code session on Requests: 14.1 s, 3 turns, 2 CodeNib tools. ▶ Watch it replay · Pinned source, transcript and setup details

Requires Python 3.10+, Git, and Claude Code or Codex. Initialization accepts uncommitted edits and preserves the checkout.

Then ask your agent: “Use CodeNib's explore_context to find where request retry behavior is implemented. Cite the files and lines.”

This builds local search and a typed symbol graph, then connects installed agent clients. CodeNib needs no model, API key, or GPU of its own; your agent uses its own model. Language toolchain and project prerequisites vary.