RepoFold

Your codebase,
explained.
Always current.

RepoFold turns every repository into a cited, searchable workspace and keeps it updated with every commit.

See how it works
Private repositoriesLine-level sourcesIncremental updates
ReadySynced 2m ago
8f2c1ad
Architecture

Architecture

Orbit is an event-driven service that converts repository changes into a continuously updated knowledge layer.

System overview

Orbit receives repository events, maps changed symbols and publishes one consistent documentation revision. Each generated statement remains connected to its source.

Runtime topology

ServiceResponsibilityState
webWorkspace and APIStateless
workerAnalysis and generationQueued
databasePages and revisionsPersistent

Request lifecycle

A signed webhook records the target commit and queues an incremental job. Files with an unchanged blob SHA are skipped before any model call.

Source-grounded by default

Only changed files and affected pages are regenerated, keeping every sync fast and reviewable.

Updated today, 10:42 UTC·commit 8f2c1ad·

One workspace.
Four ways to understand.

One minute.
Whole picture.

From connecting a repository to a cited wiki, agent answers over MCP, and documentation that follows every push. Watch it happen.

Built to be checked.

Generated documentation should never be a black box. RepoFold keeps the source, the commit, and the change history attached.

Every claim keeps its source.

Move from generated explanation to the exact implementation in one step. Citations stay pinned to the commit that produced the page.

worker/pipeline.ts8f2c1ad
42const changed = files.filter(hasNewBlob);43await regenerate(affectedPages(changed));44await revision.publish(commit);
1Used in ArchitectureLines 42–44

Only changed code moves.

Unchanged files and unaffected pages are reused.

Knowledge is versioned.

Every documentation revision follows a commit.

We keep the wiki, not your code.

Read-only access, scoped to the repositories you pick. Source streams through the indexer and is deleted the moment the job finishes. Even the snippets you open later are fetched live from GitHub, never from us.

Security and AI processing details

Your agent
reads it too.

Connect Claude Code, Codex, or Cursor over MCP. Instead of scanning the whole codebase, your agent asks the wiki and gets a short answer with exact file and line references, pinned to a commit.

claude ~/projects/xploredMCP · repofold
>where is the login flow implemented?
ask_wiki("Neilbenji/xplored", "where is the login flow…")
Mobile: mobile/src/context/AuthContext.tsx:9-23 holds the AuthProvider; token refresh lives in mobile/src/services/api.ts:215-279. Backend: routes in backend/src/routes/auth.ts, JWT middleware in backend/src/middleware/auth.ts.
1 tool call · answered from the wiki @ c62bea6 · $0.00

One endpoint, every agent.

Anything that speaks MCP: add the server URL, paste an API key from your account, done.

Answers, not exploration.

ask_wiki answers server-side from the generated knowledge layer, so your agent spends a few hundred tokens instead of reading half the repository.

Grounded and current.

Every response names the commit it describes and cites file:line ranges your agent opens locally.

Free while
in beta.

RepoFold is in open beta. Everything you see is free. We ask only for your honest feedback. Paid team plans arrive later.

Stop documenting
yesterday's code.

Connect GitHub and give your team one place to understand what exists now.