Understand unfamiliar code with evidence.

Read a Wiki of how a repository works, follow its call paths, and inspect the source behind each explanation.

No account or API key needed for the example.

A map of the psf/requests Wiki: pages as coloured nodes, joined by the references recorded between its areas.

Ask one question. Land on the exact lines.

Each step is a call the index recorded. Click one to read the source it points at. No account or API key needed.

Explore how Requests handles redirects →

Now explore your own repository.

Paste a public GitHub repository. CodeNib draws its folders as a map, plans the chapters on it, and fills each one in as its sources check out. Read chapters as they finish, then return to your saved link.

Ready Wikis open instantly. A new Wiki uses your OpenRouter account and credits, with a $0.25–$5 spending limit you choose before starting.

Hosted limits and spending details

20 MiB download, 40 MiB retained files and 4,000 files. Files over 4 MiB are skipped. A provider call already in progress can exceed your spending limit.

Check repository eligibility before connecting OpenRouter →

Want to keep exploring first? Browse ready Wikis → Publish yours on GitHub Pages with the CodeNib Wiki action.

Take that context to your coding agent.

Build a local index for Claude Code or Codex. Find definitions, follow callers and read the source in your own checkout.

python -m pip install "codenib[graph,mcp]"
codenib codegraph init /path/to/your/repo

Needs Python 3.10+, Git, and Claude Code or Codex. Uncommitted edits are fine. CodeNib runs locally here with no model, API key or GPU of its own; your agent uses its own model.

Setup and language prerequisites · Ask your agent to start with explore_context.

Requests · Claude Code + CodeNib

$ codenib codegraph init . --agent claude

Languages: python

bm25 fresh (1.92s)

symbol_graph fresh (16.49s)

CodeGraph is ready for coding agents.

MCP server: codenib-requests-b447e805b6ad

Clients: claude

> Use CodeNib's explore_context once to find where Requests strips authentication when redirecting to another host. Then call dependency_subgraph once on that function with direction impact and depth 4 to trace which public Session method reaches it.

explore_context "strip authentication headers when redirecting to different host"

sessions.py:282–300 rebuild_auth()

sessions.py:127–157 should_strip_auth()

dependency_subgraph rebuild_auth() impact depth 4

hop 1 sessions.py:159 resolve_redirects()

hop 2 sessions.py:673 Session.send()

hop 3 sessions.py:500 Session.request()

hop 4 8 public entry points

rebuild_auth (src/requests/sessions.py:282) strips the Authorization header when should_strip_auth (sessions.py:127) detects a hostname change on redirect.

Session.get/post/… (:593+) → Session.request() (:500) → Session.send() (:673) → resolve_redirects() (:159) → rebuild_auth() (:282)

14.1 s · 3 turns · 2 tools · $0.078 list-price estimate · source unchanged

Real CLI output from one recorded run, replayed with waits condensed. Every node links to its pinned source. Transcript and sources.

Give your agent the whole thread, in one read.

In preview: codenib threads reads a GitHub issue or pull request once and writes one document for your agent. The ask, the reviews, the failing checks, the linked threads and the code they point at, with no model. When the agent comes back, it gets only what changed.

codenib threads context 8024

−21% Codex · gpt-6.1-sol

−45% Claude Code · Claude Opus 5.5

Input tokens on 76 pull requests taken over after a review or a failed check, against the agent reading the thread with gh. The agents found the files to change about as often either way. Read how it works →

codenib threads boardpoll · nothing changed
  1. A

    #812Fix a short read in Reader.read()

    up to date

    Also in progress on Reader.read(): #815

  2. B

    #815Cache reads in Reader

    up to date

    Also in progress on Reader.read(): #812

  3. C

    #807Document the retry policy

    up to date

Three agents, each on its own pull request, share one store. Each is sent only the records it has not read, and two that touch the same function are told about each other.

A sketch with made-up pull requests. Each mark is one stored record; blue is one its agent has not been sent yet. See real output.

#1 in line recall and Pass@1 on ContextBench's Agent systems leaderboard.

77.90% line recall

77.60% Pass@1, 388 of 500 tasks

Official leaderboard as of October 23, 2026 (UTC). This is our research agent, not the Wiki or the code graph: it searches with glob, grep and reads. Read how it works →

14 languages, 12 with a code graph.

See what CodeNib can do with yours, from a graph that updates as files change to plain code search.

  • Pythonlive graph
  • Golive graph
  • Rustlive graph
  • C/C++live graph
  • JavaScriptlive graph
  • TypeScriptlive graph
  • C#graph
  • Javagraph
  • Rubygraph
  • PHPgraph
  • Kotlingraph
  • Scalagraph
  • live graph updates as files change
  • graph takes a fresh index to pick up changes
  • search has no definitions or callers

Registered capabilities, not the tools on your machine; codenib toolchain status shows those. Open the language matrix →

Reproduce the methods
LocAgent, Agentless, CoSIL, OrcaLoca, RepoNavigator
Explore agent integrations →
Compare the fit
grep, Serena, CodeGraph, DeepWiki
Compare repository tools →
Experimental retrieval
71.4% code-block Recall@5 on 100 real issues, 12.8 points above the same grep candidates without reranking.
Method and limitations →

Try it where you write code.