RepoPilot

Getting started

Open a repository, wait for indexing to finish, then use Overview, Search, Ask, Architecture, Impact, Topography, History, and Settings.

First-run checklist

  1. 1. Open a repository

    Paste a GitHub URL on the home page or pick one after signing in.

    Continue →

  2. 2. Wait for indexing (or re-index)

    Watch the progress pill, then use Settings → Re-index if the SHA looks stale.

    Continue →

  3. 3. Scan Overview

    Pulse board shows index health and jumps into Ask, graph, impact, and history.

    Continue →

  4. 4. Run impact or Ask

    Trace blast radius for a file, or ask a question and open Graph / Impact from citations.

    Continue →

  5. 5. Connect an MCP client

    Point your editor at RepoPilot MCP for search, impact, and Ask against the same index.

    Continue →

Analyze a public repository

  1. Go to the home page and paste a GitHub URL or owner/repo slug.
  2. RepoPilot registers the repository, clones or reads files, and starts indexing in the background.
  3. When indexing completes, you land on the dashboard at /dashboard/<repository-id>.

Example repositories you can try:

Connect GitHub (private repos)

  1. Create a GitHub OAuth App with callback URL http://localhost:3000/api/auth/callback/github (or your deployed app URL).
  2. Set GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, and SESSION_SECRET in web/.env.local.
  3. Sign in with GitHub, pick a repository from Repositories, then open Settings and click Re-index repository if needed.

Dashboard tour

Overview

Index-aware pulse board with file counts, open PRs, and hotspots. Quick actions jump to Ask, Search, Dependency Graph, Impact, and History. Use Index settings to re-index.

Dependency Graph

Real import edges with directory clustering, path tracing, neighborhood expand, import-cycle inspector, and blast overlay from Impact (?file=&blast=1).

Topography

2D directory landscape sized by hotspot score, churn, dependents, or findings — with 7d / 30d / 90d / 1y lookbacks.

Search

Hybrid lexical + semantic search. Each hit has Graph / Impact / GitHub citation actions when a repo is selected.

Ask RepoPilot

Natural-language answers with file:line citations. Open Graph, Impact, or GitHub from any citation chip. Requires an LLM provider (GROQ_API_KEY, GEMINI_API_KEY, or local Ollama) in api/.env.

Impact

File, symbol, or PR blast radius with risk factors, confidence, and a map. Deep-link into the architecture canvas with blast highlighting.

History

Indexed revision SHAs plus commit / PR history search from ingested git data.

Pull Requests

Review findings with severity filters; changed files link to Impact and Graph. Similar PRs link through to other pull details.

Settings & MCP

Live index health, re-index controls, and MCP setup with repo-scoped tool examples for agent clients.

Indexing stages

Full indexing runs these stages in order:

  1. Sync — parse files with Tree-sitter; extract symbols, imports, exports
  2. Graph — resolve module and symbol dependency edges
  3. Search — chunk files, embed text, store vectors in pgvector
  4. History — ingest recent commits for hotspots and co-change analysis

Progress appears in the floating index pill and on Overview / Settings. Demo mode (NEXT_PUBLIC_DEMO_MODE=true) skips live indexing and shows seeded UI data.

CLI indexing (advanced)

For local repos or CI, index from the command line:

./scripts/index-repo.sh owner/repo [path-to-clone]

# Opens dashboard at /dashboard/<derived-id>