VibeDrift
Summary
By session 50, your AI coding agent has quietly invented its own conventions — raw SQL next to repository abstractions, five error formats across a dozen files, auth checks that exist in half the handlers. VibeDrift tracks the patterns your codebase already follows and stops the next generated file from breaking them.
VibeDrift runs a local scan in roughly two seconds, ranks every inconsistency by how much damage it causes, and generates a fix your agent can paste directly. The MCP integration is the sharper edge: Claude Code and Cursor can query your codebase mid-task — before writing a line — asking what error pattern the repo already uses or whether a function like the one they are about to generate already exists. All analysis runs on your machine; no code leaves. The ceiling appears on teams who want cross-repo pattern enforcement or automated remediation without human review — VibeDrift surfaces the problem, it does not fix it autonomously.
Bottom line: Pick this when your AI coding sessions have grown long enough that the output no longer reads like the same developer wrote it; skip it if you need the agent to auto-remediate drift without your sign-off, because the tool finds and ranks the problems but leaves the fixing to you.
Pricing Plans
SubscriptionLast verified 2 weeks ago- Price
- $15/mo
- Free Tier
- 1 deep scan / month, unlimited local scans, free MCP tools forever
FREE
Start free. No card needed.
- 1 deep scan / month
- Unlimited local scans
- Free MCP tools, forever
- Vibe Drift Score + reports
- Scan-over-scan delta
PRO
For developers shipping every day. Most popular.
- Everything in Free, plus 12 deep scans / month
- Drift trend over time
- In-editor deep checks via MCP
- Coherence report + copy-ready fixes
- Watch mode + git pre-push gate
- Top-ups: 5 scans for $10
ENTERPRISE
Regulated, air-gapped, or self-hosted.
- Everything in Pro, plus
- Self-host in your cloud (BYOC)
- Team seats + shared dashboard
- SSO / SAML
- Custom rules + SLA
- GitHub App, auto-PR
- Dedicated support
View full pricing on vibedrift.ai →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Local-only analysis with no data leaving the machine, so codebases under NDA or with strict data-residency requirements can run scans without a legal review cycle.
- Findings are ranked by severity rather than listed flat, which means an agent or developer spending five minutes on the output addresses the highest-damage inconsistencies first instead of triaging a noise list.
- MCP server exposes queryable pattern endpoints so Claude Code or Cursor can ask what conventions the repo already follows before generating a new file — catching drift before it lands rather than cataloguing it afterward.
- The `.vibedrift/` memory folder persists declared conventions across sessions, so a new agent session starts with context about what the project has already decided instead of rediscovering patterns from scratch.
- CLI setup is a single command with no account required for the local scan, which means a developer can run it against an existing project in under a minute and immediately see what is wrong.
Cons
Sign in to edit- VibeDrift surfaces drift and generates fix suggestions, but applying them is a manual step — you paste the fix into your agent. Teams expecting automated remediation that runs without review will hit this ceiling immediately and look at linter-enforcing CI pipelines or tools that write and commit fixes directly.
- Deep scan capabilities are locked behind a paid tier; the free local scan handles the initial audit but teams needing richer analysis on large or fast-moving codebases will find the free tier insufficient before the project matures.
- There is no cross-repository pattern enforcement, so a team managing multiple services that are supposed to share conventions — shared auth patterns, consistent error contracts across microservices — gets no signal when one repo drifts relative to another. Teams with that requirement move to centralized linting rulesets or shared schema validation enforced at the API boundary instead.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- macOS, Windows, Linux (via npm)
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-26T08:28:49.816Z
Best For
Who it's for
- Developers using Claude Code, Cursor, or other MCP clients
- Teams with growing codebases maintained by AI agents
- Projects needing local-only analysis with no data leaving the machine
What it does well
- Maintaining consistent code patterns across long AI coding sessions
- Preventing style drift when multiple agents edit the same project
- Generating ranked fix lists and memory files for agent context
- Real-time validation of proposed changes via MCP queries
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare VibeDrift
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is VibeDrift free?
- VibeDrift has a permanent free tier alongside paid upgrades (paid plans from $15/mo). You can keep using a baseline version indefinitely without paying.
- Is VibeDrift open source?
- No — VibeDrift is a closed-source tool. Source code is not publicly available.
- Can I self-host VibeDrift?
- Yes. VibeDrift supports self-hosting on your own infrastructure.
- What platforms does VibeDrift support?
- VibeDrift is available on: macOS, Windows, Linux (via npm).
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Session drift is the silent failure mode of AI-assisted codebases: each file passes the linter, none of the files agree with each other. VibeDrift runs a local CLI scan against your project, identifies where patterns conflict — two error-handling styles, duplicate functions with different names, handlers missing auth that others enforce — and ranks findings by severity. Each finding ships with a copy-paste fix you hand to your agent, and a `.vibedrift/` memory folder the agent reads at the start of every subsequent session to maintain context about declared conventions.
The differentiating feature is the MCP server. Rather than generating a report you read after the damage is done, VibeDrift exposes five query tools — `get_dominant_pattern`, `find_similar_function`, `check_file_drift`, `validate_change`, and `get_intent_hints` — that compatible clients like Claude Code and Cursor call mid-task, before committing a change. The vendor states responses arrive in under a second, locally, with no login required. That turns what would be a post-hoc audit into a constraint operating inside the generation loop.
VibeDrift fits projects where the codebase is already drifting and a ranked fix list is a productive starting point, and where the team uses at least one MCP-compatible client. It does not fit teams who need a fully automated remediation pipeline, cross-repository analysis, or enforcement that runs in CI without human review — the tool is diagnostic and advisory, not autonomous. The MCP server is described as free and open source; deeper scanning is a paid-only feature.