Now inviting the first design partners

Your docs lie. Drift catches them.

Every doc in your repo makes claims about the code — endpoints, commands, auth flows, conventions, diagrams. Drift checks those claims on every pull request, flags the ones that stopped being true, and opens a PR with the fix.

README.md · CLAUDE.md · docs/architecture.md 3 stale claims · PR #482

Your docs claim

POST /api/ordersmatch
auth: session cookiesstale
CLAUDE.md: run npm teststale
diagram: Billing → Ledgerstale

Your code does

POST /api/orderstrue
auth: JWT bearer tokenstrue
scripts: vitest runtrue
Billing → Paymentstrue
Auth moved to JWT 14 commits ago. README, CLAUDE.md and the diagram still say cookies — and your coding agent reads them on every task. ✓ fix PR opened
The problem, in a real team's words

Every codebase drifts. Nobody notices until it hurts.

We read ~900 engineering docs shared through mdview. This is one of them — a team that walked their frontend by hand to find where the code contradicted their own docs. Note what drifted: not a diagram — the plain-Markdown files their team (and their coding agents) rely on every day:

“We walked the frontend code and found places where the code contradicts your own team documentation — the docs in the repo: CLAUDE.md, AGENTS.md, README.md, docs/ — and places where the docs contradict themselves.”

Frontend audit note, shared via mdview.io · translated from Russian
How it works

Three steps. No new format to learn.

Drift reads the Markdown you already write, and the code you already ship. Deterministic first — the LLM only handles the fuzzy parts.

1

Turns docs into claims

Parses README, CLAUDE.md, AGENTS.md, docs/ and diagrams into checkable claims: which endpoints exist, which commands run, which service calls which, which conventions hold.

2

Checks them against code

On every pull request, Drift derives the real routes, scripts, call graph and structure straight from the diff — no runtime, no instrumentation.

3

Flags & fixes

Where they disagree, Drift comments inline on the PR and opens a follow-up with the corrected doc — prose or Mermaid. Green check when docs and code agree.

Who it's for

Built for the people who own the docs

Platform & staff engineers

Stop being the human diff between the wiki and reality. Onboarding docs that are actually true.

Teams working with coding agents

A stale CLAUDE.md doesn't just confuse the new hire — it steers your agent wrong on every single task.

Security & review

When the docs say Billing→Ledger but the code stopped calling it, that gap is where bugs and audit findings live.