repo-sensei

● Below: fastapi/full-stack-fastapi-template at b1125d8, its 245 files, and the trace of signing in

Understand any codebase, with answers you can verify.

Ask a codebase anything and get answers that cite the lines they stand on. Trace features across layers, draw verified diagrams, and fix bugs with tests that prove it.

One question, through the whole stack

  1. Ask in plain wordsA question about the code, as you would ask a colleague.
  2. It finds the code in every layerThe page, the API client, the route, its handler and the queries.
  3. And follows the request through themAcross languages: the frontend's call is matched to the route that serves it.
  4. Each step names its linesIts file and line, and how sure it is: ● from the code itself, ◐ matched by a rule.

What happens when someone signs in?

UIAPIServiceDataLoginlogin.tsx:53useAuthuseAuth.ts:18●loginAcce…sdk.gen.ts:27●POST /api…sdk.gen.ts:28●POST /api…login.py:23◐login_acc…login.py:23●authentic…crud.py:45●get_user_…crud.py:34●usermodels.py:51●

The engine's own trace of fastapi/full-stack-fastapi-template at b1125d8: 9 hops from the page to the data, each with its lines.

  • Cites file and line

    Each claim points at the lines it stands on, at the commit it read.

  • Says when it can't tell

    When the code doesn't answer a question, the answer says so.

  • Fixes start from a failing test

    A bug is reproduced first; a patch counts once that test passes.

  • Fresh on every push

    Only what changed is indexed again; branches and pull requests too.

One index of the code, many ways to read it

  • Ask

    Questions about the code, answered from the code: each claim checked against the lines it cites, and each citation says whether they hold it up.

  • Trace

    Follow a feature from the button to the database: UI, API, services and storage, hop by hop.

  • Diagrams

    Drawn from the code's graph, each edge checked, and marked when it no longer matches.

  • Dependencies and impact

    Modules, packages and cycles, and what a change to a symbol reaches before you make it.

  • Branches and pull requests

    Read any tracked branch; answers say when what they cited has changed since.

  • Fix and change

    From a stack trace or an issue: investigated, reproduced by a failing test, planned for your approval, patched in a sandbox and verified by the tests. A change asked for in plain words is planned, approved and tested the same way.

  • Explore

    Open-source repositories, indexed and public, to read and ask about without an account.

Your code stays yours

  • Private code is read through a GitHub App, installed only on the repositories you choose.
  • Each organization's data is kept apart in the database itself, row by row.
  • Tests run in a sandbox with no internet access; only installing dependencies reaches the package registries.
  • Nothing is changed without a person approving the plan; risky plans need two.
  • Agent runs stop at a daily spending cap, and summaries at a monthly budget.
  • Changes to members, repositories, keys, integrations and fixes are in the audit log.

In your editor, through MCP

Search, trace and ask from your coding agent, signed in once with OAuth or an API key.

  • Claude Code
  • VS Code
  • Cursor
  • any MCP client

Start with one repository

Sign in with GitHub, connect a repository, and ask it the first question you have.