NAVIGATOR
Join the waitlist
AI writes the code. Someone still reads it.

Understanding
is the new bottleneck.

Your repo grows faster every week. Review queues don't. Navigator turns every change into a narrated tour — live in your editor, as a video on every pull request, as a podcast in your ears.

Join the waitlist See it work early access · launching soon
src/auth/session.ts
62export async function createSession(
63 req: Request, res: Response) {
64 const user = await verify(req.headers);
65 if (!user) return res.status(401);
66 const session = await issue(user);
67 return res.json(session);
68}
narrating · eve
“This is the moment the request becomes a real user. If verification fails we stop here — everything downstream can safely assume an authenticated caller.”
Navigator
Connected
Player Graph Transcript
STEP 3 / 7
request verify session
Stages
1. Where the request enters
2. How the caller is verified
3. Creating the session
4. What the client gets back
How authentication works · navigator
0:34 1:21
every PR ships with a narrated video

Stop reading diffs.
Watch them.

Navigator narrates every change and a video walkthrough lands as a comment before you open the diff. Reviewers arrive with context already loaded.

N navigator commented on #1482 bot
Walkthrough ready — 7 scenes, 3 files, 1:21.
1:21
day one, not month three

Every pull request explains itself.

Narrated tours in your editor. Video on every PR. A podcast for the commute. The codebase stops being tribal knowledge.

Join the waitlist Tour the features
→ Navigator · generate walkthrough
prompt: "explain how auth works"▍
✓ 7 scenes · 3 files · narrating
The problem

Code output went up. Human context didn't.

01
Diffs got bigger

Agent-written changes span files a reviewer has never opened. The diff shows what moved, never why.

02
Review became the queue

The reviewer rebuilds the author's mental model from scratch, every time, for every PR.

03
Knowledge stayed tribal

The person who understands the module is the bottleneck — and they're in a meeting.

Navigator's answer: generate the explanation as readily as the code itself — and deliver it where the work already happens.
Five surfaces

One engine. Wherever you actually are.

The same narration pipeline drives your editor, your pull requests, your headphones and your inbox — and now checks whether the reviewer actually understood the change.

Live walkthroughs

An agent drives your editor while it talks.

Ask “explain how auth works.” Navigator opens the files, highlights the exact line ranges, scrolls with the narration, and draws the node graph as the story moves through your system.

Natural language voiceover with multiple voices and adjustable playback rate.
Tours are built from your workspace, so they reflect the code actually on disk.
“Where am I?” and “Explain this” read any selection aloud in plain English.
Navigator
Connected
What do you want to walk through?
Explain how the authentication flow works
Generate graph data Voice: eve
Generate Walkthrough
Where Am I? Explain This
Walkthroughs
feat/billing-sync
Checkout → subscription sync Completed
18m ago· 2:04 Watch
fix/session-reconnect
Live session reconnect handling Analyzing
PR & MR video

The review starts before the reviewer does.

Navigator produces a fully narrated video walkthrough of every pull request and posts it as a comment. Reviewers press play.

pull requests merge requests whole-repo context replay any commit
N navigator commented 4 minutes ago bot
codefaqs/navigator #1482 · 7 scenes
Walkthrough 1:21
Completed generated automatically · no setup per PR
Comprehension gate

Prove you read it, not just approved it.

Alongside the walkthrough, Navigator can turn a pull request into a short quiz — generated straight from the diff. Reviewers answer a few questions about the change; pass, and the check turns green.

Questions reference real file paths from the diff — no generic trivia, no rubber-stamp approvals.
A commit status gates the PR — pending until someone passes, green the moment they do.
Configurable pass threshold and attempt limit — a nudge toward actually reading it, not a wall.
N navigator commented 2 minutes ago bot
codefaqs/navigator #1482 · comprehension check
Question 2 of 3 src/auth/session.ts
If verify(req.headers) returns null, what happens next?
The session is created anyway
The request is rejected with 401
The error is logged and ignored
Submit answer
Pending 2 of 3 correct so far · pass at 70% · 1 attempt left
Podcasts

Your codebase, as a two-host show.

Turn any walkthrough into a conversational episode — two hosts trading questions about your architecture. For the commute, the treadmill, the pre-standup coffee.

Ep. 12 — The render pipeline, end to end
codefaqs/navigator · 9:47
3:429:47
Briefings

Monday morning, already caught up.

Pick your repos and a schedule. Navigator gathers the week's commits, pull requests and issues, writes the summary, and delivers it by email — or as an audio briefing.

Weekly platform digest
Mondays 08:00 · email + audio
Active
24commits landed, mostly in the render pipeline
06PRs merged — billing proration was the big one
02issues opened about repo connection settings
Use cases

Four bottlenecks, gone.

Review at speed

Watch the 90-second tour, then review the lines that matter. Big AI-authored diffs stop being a wall.

New-hire onboarding

Day one, they ask the repo how auth works — and get a guided tour instead of a Slack thread.

Legacy archaeology

Replay a walkthrough against the commit it was authored on. The service nobody owns finally explains itself.

Code you can hear

On-demand aural explanation of any highlighted range, plus a spoken summary each time you open a file.

How it works

From change to explanation, in four moves.

01
A change lands

Connect a repo once. From then on, every pull request queues a walkthrough automatically.

02
Navigator reads the change

It plans the story, decides which files matter and in what order, then writes each scene — with the whole repo as context, not just the diff.

03
Voice and visuals come together

Each scene gets narration and real, syntax-highlighted code frames, assembled into a single video.

04
It shows up where you work

The finished walkthrough arrives as a comment on the pull request — no dashboard to check, nothing to go looking for.

Private by default

Your code is never used to train models, and nothing is shared between organizations.

Encrypted throughout

Credentials are encrypted at rest, and access is always scoped to the smallest permission that works.

Guarded inputs

Every input is screened before it reaches a model.

Yours alone

Your repositories stay yours — access can be revoked at any time, and removing Navigator leaves nothing behind.

Pricing · not final

Pricing, when we launch.

We're still shaping the plans. Join the waitlist and you'll hear the details first.

Free
TBD
for individuals and OSS
Live walkthroughs in your editor
Monthly PR video quota
One personal organization
Join the waitlist
Planned
Pro
TBD
for review-heavy teams
Higher walkthrough, video and podcast quotas
Whole-repo context narration
Scheduled briefings by email and audio
Team organizations with roles and invites
Join the waitlist
Enterprise
TBD
for platform and DevEx teams
Custom quotas and controls
Dedicated deployment options
Admin analytics and cost breakdowns
SSO-ready sign-in with MFA
Join the waitlist

Chart a course through every change.

Navigator is opening up soon. Leave your email and we'll let you know the moment it's available.

one email at launch · no spam, ever