RepotourBETA
apiauthrouterdb/usersdb/postswebssrclientcdnedge fn

Understand any codebase in
minutes, not weeks.

Skip the hours of file-hopping. Instead talk to an AI colleague — it sketches the architecture live and answers your questions by voice.

Try
Keep reading
01
The old way

Reading a codebase is still a click-by-click slog. Understanding a repo takes weeks.

Even with AI assistants. You ask, it answers, you scroll, you open a file, you ask again. Every question is a round trip. Every answer is a wall of text.

ai-chat.app
U
how does authentication work in this repo
AI
Authentication in this repository is handled through a multi-layered system. The primary entry point is src/auth/middleware.ts. To understand it fully, you should look at:
1. The JWT verification logic
2. The session management layer
3. The refresh token rotation
4. The RBAC policy enforcement
U
okay but where does the jwt come from
AI
Great question. JWTs in this codebase are issued by the auth service located at...
12 paragraphs, no structure
follow-up #7 of 40
Still no diagram. Still no overview.
40+
follow-up prompts
to piece together a mental model of a mid-size repo.
0
visual structure
chat is a single column. Architecture is a graph.
100%
manual navigation
you still Cmd-click through files to verify every claim.
1
modality
text-only. No voice, no diagram, no one pointing at the file that matters.
02
The RepoTour way

Less hunting for code. More understanding systems.

It's the difference between skimming a 200-page codebase alone and pulling up a chair next to the senior engineer who wrote it. You ask, they point, you see.

Alone with the code
You read docs.
You skim files.
You guess.
→ open README
→ search "entry point"
→ open src/index.ts
→ follow import
→ open src/app.ts
→ follow import
→ open src/router.ts
→ …
→ still confused
With RepoTour
You listen.
You ask.
You understand.
Guide
So the request enters at src/router.ts — watch the graph — and fans out to three handlers.
You
wait which one does the auth check
Guide
Good catch. Middleware fires first — let me highlight it.
Live· 2:34 into chapter 3
Narration, not walls of text
Architecture read aloud by a guide that actually knows what matters. You hear the shape of the system before you see any code.
Interrupt like a person
'Wait, what's that service?' Speak over it. The tour pauses, answers, and picks up where you left off.
Visuals, always
Every concept has a node. Every relationship has an edge. No more reconstructing a graph from paragraphs in your head.
03
Shipping now · v1.0

What you get today.

Paste a public repo. Get a narrated architecture tour with a live-drawing diagram. Ask anything by voice. That's it — no setup, no install, no keys.

facebook/react
vercel/next.js
tiangolo/fastapi
vuejs/core
sveltejs/kit
django/django
Supported
Public GitHub repos
Any public repo, any language. Node, Python, Go, Rust, Java, Ruby — if it's on GitHub we can tour it.
approuterauthdb
Generated live
Live-drawing diagrams
The architecture graph renders as the narration unfolds. Nodes appear when they're introduced; edges animate in with the relationship being described.
Spaceto interrupt
Voice-native
Interrupt by voice
Hold Space. Ask anything. The guide pauses, answers, and picks up the thread. No typing required — ever.
00:00
Overview
01:42
Entry points
04:05
Core logic
06:18
Data flow
10:30
Services
13:02
Tests
15:40
Extensions
Seven chapters
Guided narrative
Every tour is split into chapters — overview, entry points, core logic, data flow, extension points. Skip ahead, rewind, or scrub the transcript.
Not in v1 · yet
Private repos·Editor integration·Team workspaces·Custom voice models
See roadmap
04
Coming in v2 · Q3

Next: a colleague inside your editor.Learning & onboarding codebases has never been easier.

V2 lives on your devive or in VS Code and Cursor. It talks & guides you through the codebase. It draws diagrams and graphs in real time to explain the codebase. It opens the related files. It points at the line — all while you keep your hands off the keyboard.

auth-service
Explorer
src/
index.ts
router.ts
middleware.ts
auth/
jwt.ts
session.ts
db/
users.ts
12export function verifyJWT(token: string) {
13 const decoded = jwt.verify(token, SECRET);
14 if (!decoded.sub) throw new AuthError();
15 return decoded as TokenPayload;
16}
17
18export function issueJWT(userId: string) {
19 return jwt.sign({ sub: userId }, SECRET);
20}
Line 14 — the auth check
Repotour
Live
routerjwt.tssessiondb/users
"Every protected route runs verifyJWT first. Watch line 14 — that's where a malformed token gets rejected…"
⌘ .to talk — the tour follows your cursor
01
Native plug-in or application
Install the application or plugin once in VS Code or Cursor. Works on any repo you already have open — public or private.
02
Jumps to the line
'Where's the auth check?' — the file opens, the line highlights, the narration keeps rolling.
03
Live-generated visuals
Flow charts, sequence diagrams, dependency maps — drawn on demand for the exact question you asked.
04
Always on your team
Your private codebase, your team's vocabulary. The guide learns the repo the same way a new hire would.
05
The leap

The days of Cmd-clicking your way through
a codebase are over.

Reading code was never the goal. Understanding the system was. Days of exploration, compressed into a conversation.

2 free tours · then sign in · free during beta
V1 live now
PrivacyTermsAPIGitHub@repotour