for teams that have adopted ai coding tools

Code review is the new bottleneck.

You merge three to five times more code than you did two years ago. Your reviewers still read it the way they did in 2010 - one file at a time, with no idea why any line changed.

The unit of review should be a narrative, not a diff.

we're onboarding a small number of teams at a time.

you're on the list. we'll reach out as we open room for new teams.

the same pull request, two ways

One of these was written for a person to read.

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) {
                                            
                                                43  const s = await redis.get(req.cookies.sid);
                                            
                                                43  const token = req.headers.get('authorization');
                                            
                                                44  if (!token) return null;

← 01 the problem 03 touching the session store →

how it works

The author barely does anything new.

The story gets built from the diff the author already pushed. They shape it; they don't start from a blank page.

Open a PR

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

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.

Publish and Share

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

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.

for teams that have adopted ai coding tools.

you're on the list. we'll reach out as we open room for new teams. team size helps us decide who to bring on first.