Your AI agent gets worse as your project grows.
It forgets your patterns, repeats code, and breaks what worked. VibeDrift catches the drift before it spreads.
Same project. Two different styles.
Your AI wrote both files, in two sessions. Both pass the linter. Together they teach it your project has no rules.
import { UserRepository } from '../repositories/user';
import { requireAuth } from '../middleware/auth';
export async function getUser(req: Request) {
requireAuth(req);
const user = await UserRepository.findById(id);
if (!user) throw new NotFoundError();
return user;
}import { db } from '../config/database';
export async function getOrder(req: Request) {
const id = req.params.id;
const rows = await db.query('SELECT * FROM orders...');
if (rows.length === 0) {
return { status: 404, error: 'not found' };
}
return rows[0];
}Your agent checks before it writes.
A report tells you about drift after it lands. The VibeDrift MCP server stops it from landing at all. Mid-task, Claude Code and Cursor ask your codebase what it already does, and get an evidence-backed answer in under a second. That turns drift detection into drift prevention.
Find it, fix it, keep it clean.
One scan ranks what's wrong by how much it hurts, hands your agent a copy-paste fix, and leaves a memory it reads every session.
A .vibedrift/ folder your agent reads every session.
Your agent asks your codebase mid-task, answer in under a second.
Refreshes the memory on every save. Zero network calls.
We checked if it works. Honestly.
With and without VibeDrift, graded by an independent pass, it only changes things when the model would've gotten it wrong, and we show where it did nothing.
When the model would match your conventions anyway, the signal does nothing, and we're not hiding that.
Patterns catch the visible drift. Deep catches what they can't.
The free local scan catches the obvious drift in seconds. The deep scan reads what your code actually means, so it finds the deeper conflicts a quick scan can't, the kind that quietly pile up in big codebases.
- ✓Static + Code DNA analysis, pattern, structure, and duplicate checks, all on your machine in ~2s
- ✓Drift detectors, mismatched patterns and missing auth guards
- ✓Scaffolding detection, flags half-finished, copy-pasted code
- ✓Scan-over-scan delta, what changed since your last scan
- ✓CI-ready, fast enough for every save and pull request
Catches the stuff your code visibly does differently.
- ★Semantic duplicates, the same logic hiding under different names
- ★Intent mismatch detection, when a function's name doesn't match what it does
- ★AI-validated findings, every result is double-checked by Claude, so you don't chase false alarms
- ★Coherence report, a ranked scorecard of how consistent your code is with itself, worst first
- ★Fix prompts, a ready-to-paste fix for each finding
- ★In-editor via MCP, catches issues right as your agent writes them
Catches the conflicts you can't spot by eye, the ones hiding in what the code means.
The deep scan helps most exactly where your AI agent can't see your conventions on its own, which is right when drift creeps in.
Free to start. Pay only for deep scans.
Local scans and the local MCP tools are free on every plan, forever. Paid plans add a deep-scan budget and in-editor checks.
Out of deep scans? Top up 5 for $10, on any plan. Credits never expire.
Questions, answered.
How do I get started?+
Run npx @vibedrift/cli . in any project, no account, no config. Local scans are free and unlimited; sign in only when you want a deep scan or the dashboard.
Does it auto-fix, or just flag drift?+
Both. Every scan writes copy-ready fix prompts to .vibedrift/fix-plan.md so you, or your agent, can apply them. Deep scans add AI-synthesized fixes for the contradictions patterns can't see.
What's the Vibe Drift Score?+
A 0–100 score across five categories, graded against your own codebase's dominant patterns, not a generic rulebook. It tells you how internally consistent your project is and which files drag it down.
Is it really open source?+
Yes. The local scanner is MIT-licensed at github.com/VibeDrift/VibeDrift.
Stop blaming the model.
See what your codebase has been teaching your AI.
Not ready to scan? Get notified of updates.