Narrate

the problem

Code review hasn't caught up

01

3–5x more code

Agents generate it faster than any human can read it. The volume isn't slowing down.

+3,200−540in one afternoon
02

Context lives three tabs away

The "why" is in Linear, Notion, Slack. Never next to the diff. Reviewers have to reconstruct it from scratch.

linearnotionslack— not the diff
03

Reviewers click in, then click away

A 40-file diff with no thread. So it sits open for days while the author waits.

open · waiting 4 days

the same pull request, two ways

One of these was written for a person to read.

We make the why travel with the change, giving you the full story.

before a list of files to click through

files changed +1,204 −312 · 7 files

src/server/session/store.ts+182−47

src/middleware/auth.ts+3−2

src/workers/presence.ts+31−48

src/workers/billing.ts+8−12

src/cli/impersonate.ts+6−9

src/__tests__/session.test.ts+96−0

src/__tests__/presence.test.ts+22−0

where do you start? what changed first? the list won't say.

after a narrated walkthrough

02 / 05

02 / 05 3 files · +47 −12

section ii

Migrating the auth middleware

The legacy session check ran on every request, hitting Redis even for unauthenticated routes. We replaced it with a token flow that short-circuits when no auth header is present.

src/middleware/auth.ts L42 — L46

 42export async function authenticate(req) { 
const s = await redis.get(req.cookies.sid); 
const token = req.headers.get('authorization'); 
if (!token) return null; 

← 01 the problem 03 touching the session store →

how it works

Seamless curation for the author.

The outline gets built from the diff the author already pushed. They shape it into something worth sharing.

01feature/auth → main

Open a PR

Push your branch and open the PR the way you already do.

023 sections drafted

Narrate drafts, you edit

It groups the diff into sections, orders them so they build on each other, and writes a first pass of the prose between them.

✓ approved

03read top to bottom

Publish and share

Reviewers read top to bottom, like a chapter. They understand the change as a whole - and approve in a single pass.

why it matters

AI review tools optimize for approval. We optimize for comprehension.

They don't make the team understand the change. Every rubber-stamped diff is comprehension debt that compounds. We're not here to review code faster than you. We're here to make sure a human actually understood it. That's the only velocity that lasts.

questions

Common questions.

Do I have to write the narrative myself?

No. The AI drafts it from your diff and linked context; you spend a few minutes editing.

Does this replace GitHub?

No. Comments and approvals all sync two-way.

What if the AI draft is not what I want?

You're in the driver's seat. Editing a draft is seamless, and you publish only when it's right.

early access

Get early access

We're opening Narrate to a small number of teams. Leave your email and we'll be in touch as room opens up.

Code review, written to be read.